Triple
T34949770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balladonia |
E1007956
|
entity |
| Predicate | isAlongRoute |
P120265
|
FINISHED |
| Object | Perth–Adelaide road route |
—
|
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: Perth–Adelaide road route | Statement: [Balladonia, isAlongRoute, Perth–Adelaide road route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlongRoute Context triple: [Balladonia, isAlongRoute, Perth–Adelaide road route]
-
A.
hasAlongRoute
chosen
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
B.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
D.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
-
E.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782ccb1ec8190a15e00c9e678e5da |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.