Triple
T27282283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crosby Reid |
E688368
|
entity |
| Predicate | familyResidenceHistory |
P168945
|
FINISHED |
| Object | United States of America |
—
|
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: United States of America | Statement: [Crosby Reid, familyResidenceHistory, United States of America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyResidenceHistory Context triple: [Crosby Reid, familyResidenceHistory, United States of America]
-
A.
hasNearbyFormerResidenceOf
Indicates that one entity is located near a place that used to be the residence of another entity.
-
B.
hasAncestralResidence
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
C.
formerResidenceOf
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
-
D.
residenceDuringLife
Indicates that an entity lived or resided in a particular place during some period of its lifetime.
-
E.
otherResidence
Indicates that an entity has an additional or alternative place of residence beyond its primary home.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 11:08 a.m.