Triple
T7516674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Twain Tonight! |
E177662
|
entity |
| Predicate | longRunning |
P40952
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mark Twain Tonight!, longRunning, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longRunning Context triple: [Mark Twain Tonight!, longRunning, true]
-
A.
longRunningProduction
Indicates a production process or operation that continues for an extended duration, typically beyond normal or expected timeframes.
-
B.
isLongRunning
Indicates that an action, process, or operation continues for an extended duration, typically longer than is usual or expected.
-
C.
longRunningShow
chosen
Indicates that a show has been running for an extended period of time, typically across many episodes or seasons.
-
D.
runsMostly
Indicates that an entity performs running as its primary or most frequent activity compared to other activities.
-
E.
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.
- 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_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. |
Created at: March 27, 2026, 3:46 p.m.