Triple
T38058183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serie A 2005–06 with Inter Milan |
E950261
|
entity |
| Predicate | governingBodyDecisionDate |
P2232
|
FINISHED |
| Object | 2006-07-26 |
—
|
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: 2006-07-26 | Statement: [Serie A 2005–06 with Inter Milan, governingBodyDecisionDate, 2006-07-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyDecisionDate Context triple: [Serie A 2005–06 with Inter Milan, governingBodyDecisionDate, 2006-07-26]
-
A.
decisionDate
chosen
Indicates the date on which a specific decision was formally made or finalized.
-
B.
decisionAdoptedAt
Indicates that a decision was formally adopted or approved at a specific time or event.
-
C.
decreeRecordedOn
Indicates that a formal decree has been officially recorded or entered into the record on a specific date.
-
D.
decisionEffectiveDate
Indicates the date on which a particular decision becomes valid, operative, or officially takes effect.
-
E.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.