Triple
T28763957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A3 road |
E726202
|
entity |
| Predicate | capitalConnected |
P152160
|
FINISHED |
| Object | Douglas |
—
|
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: Douglas | Statement: [A3 road, capitalConnected, Douglas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalConnected Context triple: [A3 road, capitalConnected, Douglas]
-
A.
connectsCapitalWith
chosen
Indicates a relationship where something serves as a link or route between a capital city and another place or entity.
-
B.
connectsCapital
Indicates a relationship where one entity serves as the capital city that is officially linked to or associated with another entity, such as a country or region.
-
C.
hasCapitalConnected
Indicates that there is a direct connection or linkage between an entity and its capital city.
-
D.
capital
Indicates that one place serves as the official seat of government or primary administrative center for another political entity.
-
E.
capitalPossiblyAt
Indicates a possible or uncertain capital relationship, where one location may be the capital of another but this is not definitively established.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 6:12 a.m.