Triple
T5273108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patton (1970 film score) |
E119307
|
entity |
| Predicate | trackIncludes |
P22382
|
FINISHED |
| Object | Main Title from Patton |
—
|
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: Main Title from Patton | Statement: [Patton (1970 film score), trackIncludes, Main Title from Patton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackIncludes Context triple: [Patton (1970 film score), trackIncludes, Main Title from Patton]
-
A.
tracks
Indicates that one entity monitors, follows, or keeps a record of another entity’s state, behavior, or progress over time.
-
B.
followsInTracklist
Indicates that one item directly comes after another in an ordered tracklist sequence.
-
C.
tracksIndex
Indicates that one entity maintains or records the position, order, or index of another entity within a sequence or collection.
-
D.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
E.
seriesIncludes
chosen
Indicates that a particular series contains or encompasses the referenced item as one of its constituent parts.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.