Triple
T38058170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serie A 2005–06 with Inter Milan |
E950261
|
entity |
| Predicate | pointsOnPitch |
P170115
|
FINISHED |
| Object | 76 |
—
|
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: 76 | Statement: [Serie A 2005–06 with Inter Milan, pointsOnPitch, 76]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsOnPitch Context triple: [Serie A 2005–06 with Inter Milan, pointsOnPitch, 76]
-
A.
points
Indicates that one entity directs attention, focus, or a physical/abstract indication toward another entity or location.
-
B.
afPoints
chosen
Indicates a relationship where a scoring or point value is assigned, tracked, or associated with an entity or interaction.
-
C.
relativePositionInStadium
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
D.
ballPlacement
Indicates the spatial positioning or arrangement of a ball relative to a reference point, object, or area.
-
E.
pointsType
Indicates that one entity is classified as a specific type or category of points associated with another entity.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:21 p.m.