Triple
T1683886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic world |
E36398
|
entity |
| Predicate | includesProcess |
P13114
|
FINISHED |
| Object | colonial expansion |
—
|
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: colonial expansion | Statement: [Atlantic world, includesProcess, colonial expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesProcess Context triple: [Atlantic world, includesProcess, colonial expansion]
-
A.
processIncludes
chosen
Indicates that a process contains, encompasses, or incorporates another process or subprocess as part of its overall execution or structure.
-
B.
hasProcess
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
C.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
D.
includesServiceFor
Indicates that one entity’s offering or package contains or covers a particular service provided for another entity.
-
E.
includesStandard
Indicates that one entity contains, incorporates, or makes use of a particular standard as part of its definition, implementation, or specification.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.