Triple
T35994826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington District |
E1040950
|
entity |
| Predicate | partOfLater |
P38393
|
FINISHED |
| Object | Territory South of the River Ohio |
—
|
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: Territory South of the River Ohio | Statement: [Washington District, partOfLater, Territory South of the River Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLater Context triple: [Washington District, partOfLater, Territory South of the River Ohio]
-
A.
partOfAfter
chosen
Indicates that one entity becomes a component or subset of another entity at some point after a specified time or event.
-
B.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
C.
basedInLater
Indicates that an entity is located or headquartered in a place during a later time period or phase, relative to some earlier location or state.
-
D.
laterArrangementFor
Indicates that one arrangement, plan, or setup occurs after and supersedes another in time.
-
E.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00b7fb90f881908f73edf2be8cc3a5 |
completed | May 10, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_6a00b75593d08190b3e76191cd79cdec |
completed | May 10, 2026, 4:50 p.m. |
Created at: May 3, 2026, 4:07 p.m.