Triple
T27868585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lou's Cafe |
E704427
|
entity |
| Predicate | successorInStoryWorld |
P190996
|
FINISHED |
| Object | Lou's Aerobic Fitness Center |
—
|
NE NERFINISHED |
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: Lou's Aerobic Fitness Center | Statement: [Lou's Cafe, successorInStoryWorld, Lou's Aerobic Fitness Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInStoryWorld Context triple: [Lou's Cafe, successorInStoryWorld, Lou's Aerobic Fitness Center]
-
A.
successorAct
Indicates that one action or event directly follows and replaces another in a sequence or process.
-
B.
successorSeries
Indicates that one series directly follows another in sequence, continuing or extending it as its successor.
-
C.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
-
D.
successorInDomain
Indicates that one entity directly follows another in a specified ordered domain or sequence.
-
E.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: April 27, 2026, 6:22 p.m.