Triple
T32407275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beyoncé’s 2018 Coachella performance |
E828116
|
entity |
| Predicate | setLength |
P266
|
FINISHED |
| Object | approximately two hours |
—
|
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 two hours | Statement: [Beyoncé’s 2018 Coachella performance, setLength, approximately two hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setLength Context triple: [Beyoncé’s 2018 Coachella performance, setLength, approximately two hours]
-
A.
restoresLength
Indicates that an action or process returns something to its original or intended length.
-
B.
usableLength
Indicates the portion of an object’s total length that can actually be used for its intended function or purpose.
-
C.
cellLength
Indicates the measured extent of a cell from one end to the other, typically along its longest axis.
-
D.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
E.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c24ca0f08190a5b2c1d32205eaee |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:53 a.m.