Triple
T13588155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nederlandsch-Indische Spoorweg Maatschappij |
E324622
|
entity |
| Predicate | primaryContinentOfOperation |
P8233
|
FINISHED |
| Object | Asia |
—
|
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: Asia | Statement: [Nederlandsch-Indische Spoorweg Maatschappij, primaryContinentOfOperation, Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryContinentOfOperation Context triple: [Nederlandsch-Indische Spoorweg Maatschappij, primaryContinentOfOperation, Asia]
-
A.
continentOfUse
Indicates the continent where something is primarily used or in effect.
-
B.
continentOfActivity
chosen
Indicates the continent on which an entity primarily operates, is active, or conducts its main activities.
-
C.
operatesToContinents
Indicates that an entity conducts or provides operations or services that extend across or are directed toward multiple continents.
-
D.
continentOfOffice
Indicates the continent on which a given office is geographically located.
-
E.
primaryTerritory
Indicates that a specified area or region is the main or most important territory associated with an entity.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb054c6008190839384ce26e8f71a |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.