Triple
T32311345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santee |
E825506
|
entity |
| Predicate | postContactHistory |
P173958
|
FINISHED |
| Object | subject to forced removals |
—
|
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: subject to forced removals | Statement: [Santee, postContactHistory, subject to forced removals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postContactHistory Context triple: [Santee, postContactHistory, subject to forced removals]
-
A.
historicalContactWith
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
B.
postContactOutcome
Indicates the result or status that occurs after a contact or interaction has taken place.
-
C.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
D.
recentHistory
Indicates that one entity represents the most recent sequence of events, states, or interactions associated with another entity.
-
E.
interactionHistory
Indicates that there has been one or more past interactions or exchanges between the related entities, typically capturing their sequence, timing, and possibly outcomes.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdb74c708190833b4c7d332b1a0d |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:46 a.m.