Triple
T12694097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian market process approach |
E303283
|
entity |
| Predicate | viewsCompetitionAs |
P106374
|
FINISHED |
| Object | rivalrous process |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: rivalrous process | Statement: [Austrian market process approach, viewsCompetitionAs, rivalrous process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsCompetitionAs Context triple: [Austrian market process approach, viewsCompetitionAs, rivalrous process]
-
A.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
B.
coveredCompetition
Indicates that an entity reported on, documented, or provided media coverage of a particular competition or contest.
-
C.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
D.
overseesCompetition
Indicates that one entity has responsibility for supervising, managing, or administering a competition involving another entity.
-
E.
featuredInCompetition
Indicates that an entity was included or showcased as a participant or entry in a specific competition.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96297b81c819081ad1432dc5f15f4 |
completed | April 10, 2026, 8:50 p.m. |
Created at: April 9, 2026, 5:22 p.m.