Triple
T7288703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tubular Bells |
E163938
|
entity |
| Predicate | sideOneLength |
P75403
|
FINISHED |
| Object | approximately 25 minutes |
—
|
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: approximately 25 minutes | Statement: [Tubular Bells, sideOneLength, approximately 25 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOneLength Context triple: [Tubular Bells, sideOneLength, approximately 25 minutes]
-
A.
sideOneStructure
Indicates that the specified structure is located on or associated with the first (designated "one") side of a bilateral or two-sided entity or relationship.
-
B.
firstLeg
Indicates that one entity represents the initial segment or starting portion of a multi-part journey, sequence, or process involving another entity.
-
C.
baseLengthOriginal
Indicates the original or initial length value of a base element before any changes or transformations.
-
D.
sideArchWidth
Indicates the width measurement of a side arch in a structure or object.
-
E.
side2
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
- F. None of above. chosen
Provenance (4 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb6bde448190b52852c916a8059d |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e82b0f9881909d29c99af1ea0dbf |
completed | March 27, 2026, 8:27 p.m. |
Created at: March 27, 2026, 3 p.m.