Triple
T26382388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harefield |
E663168
|
entity |
| Predicate | nearestServiceCentre |
P38419
|
FINISHED |
| Object | Junee |
E22225
|
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: Junee | Statement: [Harefield, nearestServiceCentre, Junee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestServiceCentre Context triple: [Harefield, nearestServiceCentre, Junee]
-
A.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
B.
hasServiceCenter
chosen
Indicates that an entity maintains or is associated with a service center that provides support, repair, or maintenance services.
-
C.
isServiceCentreFor
Indicates that one entity functions as a service center that provides support, maintenance, or related services for another entity.
-
D.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
E.
administrativeCentreNearby
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a119a7b0a788190a4a22685d2fa8388 |
completed | May 23, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 11:19 p.m.