Triple
T37331460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ice Age (Act I) |
E926761
|
entity |
| Predicate | placeInStructure |
P6115
|
FINISHED |
| Object | first of three acts |
—
|
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 of three acts | Statement: [Ice Age (Act I), placeInStructure, first of three acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInStructure Context triple: [Ice Age (Act I), placeInStructure, first of three acts]
-
A.
locatedOnStructureType
Indicates that an entity is situated on or supported by a particular type of structure.
-
B.
locationOfStructure
Indicates that a particular structure is situated at or occupies a specific location.
-
C.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
D.
positionStructure
Indicates a spatial or organizational arrangement relationship, specifying how one structure is positioned or configured relative to another.
-
E.
placeInSeries
chosen
Indicates the position or order that something occupies within a sequence or series.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:16 p.m.