Triple
T7516693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Twain Tonight! |
E177662
|
entity |
| Predicate | runSpan |
P77424
|
FINISHED |
| Object | performed over several decades |
—
|
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: performed over several decades | Statement: [Mark Twain Tonight!, runSpan, performed over several decades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runSpan Context triple: [Mark Twain Tonight!, runSpan, performed over several decades]
-
A.
runsBetween
Indicates a relationship where something extends, operates, or connects from one point, entity, or state to another along a path or interval.
-
B.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
-
C.
runBy
Indicates that an entity is operated, managed, or controlled by another entity.
-
D.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
E.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5f595148190b36649b0095bb898 |
completed | March 27, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:46 p.m.