Triple
T33814596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Highway 2 |
E866635
|
entity |
| Predicate | connectsMajorSubregions |
P24718
|
FINISHED |
| Object | Indochina |
—
|
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: Indochina | Statement: [Asian Highway 2, connectsMajorSubregions, Indochina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsMajorSubregions Context triple: [Asian Highway 2, connectsMajorSubregions, Indochina]
-
A.
connectsRegions
chosen
Indicates a relationship where one entity links or joins two or more distinct regions, enabling passage, interaction, or continuity between them.
-
B.
shareMajorCityRegion
Indicates that two entities are associated with the same major city or its surrounding metropolitan region.
-
C.
connectsRemoteAreaToMajorCity
Indicates a relationship where a route, service, or infrastructure links a remote or rural area directly to a major city.
-
D.
isMajorRegionFor
Indicates that a region serves as a primary or significant area associated with a particular entity, activity, or phenomenon.
-
E.
connectsMetroAreas
Indicates a relationship where a transportation route or service links two or more metropolitan areas, enabling direct travel or interaction between them.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 1, 2026, 1:46 a.m.