Triple
T36320370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cynthia Ann Parker |
E894313
|
entity |
| Predicate | placeOfRecapture |
P195018
|
FINISHED |
| Object | near Pease River, 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: near Pease River, Texas | Statement: [Cynthia Ann Parker, placeOfRecapture, near Pease River, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfRecapture Context triple: [Cynthia Ann Parker, placeOfRecapture, near Pease River, Texas]
-
A.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
B.
capturedPlace
Indicates that an agent took control of or seized a specific place, typically through force or strategic action.
-
C.
recapturedInConflict
Indicates that an entity was taken back or regained during a specific conflict or war after previously being lost or captured.
-
D.
cityRecapturedFrom
Indicates that control of a city has been regained by one party from another party that previously held it.
-
E.
recapturedUnder
Indicates that an entity was captured again while under a specific authority, condition, or legal framework.
- 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_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: May 3, 2026, 4:09 p.m.