Triple
T10710708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lackawaxen, Pennsylvania |
E252526
|
entity |
| Predicate | ZaneGreyLivedAndWorkedHere |
P47389
|
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: [Lackawaxen, Pennsylvania, ZaneGreyLivedAndWorkedHere, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ZaneGreyLivedAndWorkedHere Context triple: [Lackawaxen, Pennsylvania, ZaneGreyLivedAndWorkedHere, true]
-
A.
laterLivedIn
Indicates that one entity resided in a particular place during a later period of its life, after an earlier residence elsewhere.
-
B.
hasWorksLocatedIn
Indicates that the works or creations associated with an entity are situated or stored in a specified location.
-
C.
creatorLivedIn
chosen
Indicates that the person who created a work resided in a particular place for some period of time.
-
D.
EasternView
Indicates a spatial relationship where one entity is oriented toward, faces, or has a view in the eastern direction relative to another reference point or area.
-
E.
hasBranchInFictionalLocation
Indicates that an organization maintains a branch, office, or presence within a fictional or imaginary location.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe523de08190a82c8f057fe8baf6 |
completed | April 9, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.