Triple
T22534694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live in Texas |
E557124
|
entity |
| Predicate | runningTimeCD |
P1958
|
FINISHED |
| Object | approx. 70 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: approx. 70 minutes | Statement: [Live in Texas, runningTimeCD, approx. 70 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runningTimeCD Context triple: [Live in Texas, runningTimeCD, approx. 70 minutes]
-
A.
runsFor
Indicates that an entity performs a running activity on behalf of, or as a representative of, another entity (such as a team, organization, or cause).
-
B.
hasRunningTimeCategory
Indicates that an entity is associated with a specific category based on its running time or duration.
-
C.
runtimeMinutes
chosen
Indicates the total duration of something, typically a media work or process, measured in minutes.
-
D.
playTime
Indicates the duration or specific time period during which an entity engages in playing or recreational activity with another entity or object.
-
E.
runsFrom
Indicates that one entity flees or escapes away from 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed952f48190b63225e7de131679 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.