Triple
T30672914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nukâka Coster-Waldau |
E780838
|
entity |
| Predicate | competitionRanking |
P103031
|
FINISHED |
| Object | 19th place at Miss Universe 1990 |
—
|
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: 19th place at Miss Universe 1990 | Statement: [Nukâka Coster-Waldau, competitionRanking, 19th place at Miss Universe 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionRanking Context triple: [Nukâka Coster-Waldau, competitionRanking, 19th place at Miss Universe 1990]
-
A.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
B.
rankingPositions
chosen
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
-
C.
globalRanking
Indicates the position or status of an entity relative to all comparable entities worldwide according to some ranking criteria.
-
D.
competitiveRecord
Indicates the win–loss (and possibly tie) outcomes between entities that have competed against each other.
-
E.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
- F. None of above.
Provenance (3 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 8:32 p.m.