Triple
T30476183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messageries Maritimes building |
E775449
|
entity |
| Predicate | cityDuringColonialEra |
P169470
|
FINISHED |
| Object | Saigon |
—
|
NE NERFINISHED |
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: Saigon | Statement: [Messageries Maritimes building, cityDuringColonialEra, Saigon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDuringColonialEra Context triple: [Messageries Maritimes building, cityDuringColonialEra, Saigon]
-
A.
foundedInColonialEra
Indicates that the entity was established or came into existence during a historical period of colonial rule.
-
B.
functionDuringColonialEra
Indicates that the function, role, or activity occurred or was in effect during the colonial era.
-
C.
placeOfColonialActivity
Indicates the location where a colonial power conducted or exercised its colonial activities or influence.
-
D.
hasCapitalDuringColonialPeriod
Indicates that a specified location served as the capital of a political entity during its colonial period.
-
E.
colonialEraHomeland
Indicates the place that served as an entity’s primary homeland or governing center during the colonial era.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687192fc88190abd451b2941b421e |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:11 p.m.