Triple
T34949711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocklebiddy |
E1007954
|
entity |
| Predicate | serviceRadius |
P104835
|
FINISHED |
| Object | large stretch of Eyre Highway |
—
|
LITERAL 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: large stretch of Eyre Highway | Statement: [Cocklebiddy, serviceRadius, large stretch of Eyre Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceRadius Context triple: [Cocklebiddy, serviceRadius, large stretch of Eyre Highway]
-
A.
areaOfService
chosen
Indicates the geographic or functional region within which a service is provided or applicable.
-
B.
neighborhoodRadius
Indicates the maximum distance around a reference entity within which other entities are considered to be in its neighborhood.
-
C.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
D.
chargeRadius
Indicates the characteristic radial distance around an entity within which its electric charge or charge-related influence is considered effective.
-
E.
serviceAreaName
Indicates the designated name of the geographic or functional area that a service covers or operates within.
- 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_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4 p.m.