Triple
T38058183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serie A 2005–06 with Inter Milan |
E950261
|
entity |
| Predicate | governingBodyDecisionDate |
—
|
GENERATED |
| Object | 2006-07-26 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 3, 2026, 4:21 p.m.