Triple
T34401816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giurgiu County |
E882997
|
entity |
| Predicate | hasMajorTransportLink |
P87781
|
FINISHED |
| Object | Giurgiu–Ruse Bridge |
E359721
|
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: Giurgiu–Ruse Bridge | Statement: [Giurgiu County, hasMajorTransportLink, Giurgiu–Ruse Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorTransportLink Context triple: [Giurgiu County, hasMajorTransportLink, Giurgiu–Ruse Bridge]
-
A.
isMajorTransportLinkIn
Indicates that a transport route or connection serves as a primary or significant transportation link within a specified area or region.
-
B.
isMajorTransportLink
chosen
Indicates that something serves as a primary or highly significant route or connection for transporting people or goods between places.
-
C.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
D.
hasGoodTransportLinks
Indicates that a place is well connected to other locations by efficient and convenient transport options.
-
E.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01a48fbbd481908ccf75551dcf4647 |
completed | May 11, 2026, 9:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a370dcbeb9c8190bbf66e26331779b9 |
completed | June 20, 2026, 10:01 p.m. |
| PD | Predicate disambiguation | batch_6a01a2d6db208190b11c1af601a544f5 |
completed | May 11, 2026, 9:35 a.m. |
Created at: May 1, 2026, 1:59 a.m.