Triple
T36320371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cynthia Ann Parker |
E894313
|
entity |
| Predicate | forcedResidence |
P185405
|
FINISHED |
| Object | Anglo-American settlements in Texas |
—
|
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: Anglo-American settlements in Texas | Statement: [Cynthia Ann Parker, forcedResidence, Anglo-American settlements in Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedResidence Context triple: [Cynthia Ann Parker, forcedResidence, Anglo-American settlements in Texas]
-
A.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
B.
ownedResidence
Indicates that one entity has ownership of a dwelling or place of residence associated with another entity.
-
C.
grantedResidence
Indicates that one entity has officially conferred the right to reside or live in a place or jurisdiction to another entity.
-
D.
intendedResidence
Indicates that one entity is designated or planned to serve as the place where another entity will live or reside.
-
E.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
- 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:09 p.m.