Triple
T9050345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tân Sơn Nhất area |
E216865
|
entity |
| Predicate | transportModePresent |
P86086
|
FINISHED |
| Object | road transport |
—
|
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: road transport | Statement: [Tân Sơn Nhất area, transportModePresent, road transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModePresent Context triple: [Tân Sơn Nhất area, transportModePresent, road transport]
-
A.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
C.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
D.
transportModeIntegration
Indicates that different modes of transportation are coordinated or combined to enable seamless or efficient movement within a journey or transport system.
-
E.
transportModeImportant
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b52cc1881909fb011d9a8af2e18 |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:10 p.m.