Triple
T28795012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North–South high-speed railway (proposed) |
E727061
|
entity |
| Predicate | ownerPlanned |
P141920
|
FINISHED |
| Object | Government of Vietnam |
—
|
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: Government of Vietnam | Statement: [North–South high-speed railway (proposed), ownerPlanned, Government of Vietnam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerPlanned Context triple: [North–South high-speed railway (proposed), ownerPlanned, Government of Vietnam]
-
A.
hasPlannedOwner
chosen
Indicates that an entity is intended or scheduled to become the owner of another entity in the future.
-
B.
operatorPlanned
Indicates that an operator has scheduled or arranged a specific action, process, or operation to occur.
-
C.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
E.
spanPlannedBy
Indicates that a time span or interval is scheduled, organized, or arranged by a particular agent or planner.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 6:25 a.m.