Triple
T19930450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modena Cemetery |
E479037
|
entity |
| Predicate | designCompetitionResult |
P8651
|
FINISHED |
| Object | first prize |
—
|
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: first prize | Statement: [Modena Cemetery, designCompetitionResult, first prize]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designCompetitionResult Context triple: [Modena Cemetery, designCompetitionResult, first prize]
-
A.
designCompetitionWonBy
Indicates that a particular design competition was won by a specified participant or entity.
-
B.
architecturalCompetition
Indicates that there is a formal design contest held to select among competing architectural proposals or architects for a specific project or purpose.
-
C.
competitionResult
chosen
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
-
D.
competitionEnd
Indicates that a competitive event or contest has concluded or reached its final state.
-
E.
programCompetition
Indicates a competitive relationship between programs, where programs are compared or ranked against each other in some contest or evaluation.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a13265c8190bc01d3af5bd658d7 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.