Triple
T13588496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indonesian railway network |
E324631
|
entity |
| Predicate | historicalBuilder |
P110179
|
FINISHED |
| Object | Dutch colonial administration |
—
|
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: Dutch colonial administration | Statement: [Indonesian railway network, historicalBuilder, Dutch colonial administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalBuilder Context triple: [Indonesian railway network, historicalBuilder, Dutch colonial administration]
-
A.
historicalReconstruction
Indicates the process of recreating or inferring past events, conditions, or states of affairs based on available evidence or records.
-
B.
historicalBase
Indicates that one entity serves as the original or foundational source, model, or precedent upon which the other entity is historically based.
-
C.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
D.
historicalField
Indicates that one entity’s field of study, work, or relevance is situated within the historical domain or concerns past events.
-
E.
historicalRecord
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb055cc98819091fab597b69e5e3e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf9f3bdc8190838539aaef1f422b |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:49 p.m.