Triple
T17099493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llanview, Pennsylvania |
E414940
|
entity |
| Predicate | usedAgainIn |
P91997
|
FINISHED |
| Object | 2013 online revival of One Life to Live |
—
|
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: 2013 online revival of One Life to Live | Statement: [Llanview, Pennsylvania, usedAgainIn, 2013 online revival of One Life to Live]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAgainIn Context triple: [Llanview, Pennsylvania, usedAgainIn, 2013 online revival of One Life to Live]
-
A.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
B.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
C.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
D.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
E.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc00880481909cc0dbc169663a41 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.