Triple
T10186712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Fort Wayne (1809) |
E236928
|
entity |
| Predicate | cessionLocation |
P92596
|
FINISHED |
| Object | present-day Indiana |
—
|
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: present-day Indiana | Statement: [Treaty of Fort Wayne (1809), cessionLocation, present-day Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cessionLocation Context triple: [Treaty of Fort Wayne (1809), cessionLocation, present-day Indiana]
-
A.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
-
B.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
C.
immediateAftermathLocation
Indicates the location where the direct and immediate consequences of an event take place.
-
D.
escapeLocation
Indicates that an entity moves away from or leaves a location to avoid danger, capture, or an undesirable situation.
-
E.
exileLocation
Indicates the place or destination to which an entity is sent or kept in exile.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded790b488190b1ed4645554873cd |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:12 p.m.