Triple
T9651331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transcaspia |
E233339
|
entity |
| Predicate | incorporationCompletedBy |
P89430
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Transcaspia, incorporationCompletedBy, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporationCompletedBy Context triple: [Transcaspia, incorporationCompletedBy, late 19th century]
-
A.
incorporationAfter
Indicates that one entity is incorporated or formally established at a later time than another entity.
-
B.
incorporatedThrough
Indicates that one entity was formed, established, or legally created by means of another specified process, mechanism, or intermediary entity.
-
C.
incorporatedIntoOnDate
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
D.
laterIncorporatedInto
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
E.
incorporatedAs
Indicates that an organization has been legally formed and registered under a specific corporate structure or name.
- 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9baf9a1c819098c407ea7d42e6d1 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:13 p.m.