Triple
T5257371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wall |
E118733
|
entity |
| Predicate | competitionWonBy |
P8326
|
FINISHED |
| Object | Maya Lin design in 1981 competition |
—
|
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: Maya Lin design in 1981 competition | Statement: [The Wall, competitionWonBy, Maya Lin design in 1981 competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionWonBy Context triple: [The Wall, competitionWonBy, Maya Lin design in 1981 competition]
-
A.
competitionWonWith
Indicates that a competition was won using, involving, or in association with a particular participant, method, tool, or resource.
-
B.
eventWon
Indicates that an entity has achieved victory or first place in a specified event or competition.
-
C.
seasonOfCompetitionWon
Indicates the specific season of a competition in which an entity achieved a victory or championship.
-
D.
winnerPlaysIn
Indicates that the entity identified as the winner of a contest or match participates in a subsequent game, round, or event.
-
E.
hasWonCompetition
chosen
Indicates that an entity has achieved victory in a competition or contest against others.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.