Triple
T33957430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian transport network |
E870617
|
entity |
| Predicate | hasCoreAxis |
P68472
|
FINISHED |
| Object | East–West Highway (Georgia) |
E17507
|
NE 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: East–West Highway (Georgia) | Statement: [Georgian transport network, hasCoreAxis, East–West Highway (Georgia)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreAxis Context triple: [Georgian transport network, hasCoreAxis, East–West Highway (Georgia)]
-
A.
hasCentralAxis
chosen
Indicates that one entity serves as the primary central axis or line of symmetry around which another entity is organized, aligned, or structured.
-
B.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
C.
hasIntermediateAxisLength
Indicates that an entity is associated with a specific value representing the length of its intermediate (middle-sized) axis.
-
D.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
E.
hasAxisCount
Indicates that an entity is associated with a specified number of axes.
- F. None of above.
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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3689e1936c81908bda86bb57edc7cc |
completed | June 20, 2026, 12:38 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.