Triple
T24219113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOA |
E601395
|
entity |
| Predicate | adminAreaLevel |
P87046
|
FINISHED |
| Object | council area of South Ayrshire |
—
|
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: council area of South Ayrshire | Statement: [NOA, adminAreaLevel, council area of South Ayrshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminAreaLevel Context triple: [NOA, adminAreaLevel, council area of South Ayrshire]
-
A.
adminTerritory
Indicates that one entity serves as the administrative authority or governing jurisdiction over a specified territory.
-
B.
adminStatus
Indicates that an entity holds an administrative role, privilege level, or state within a system or context.
-
C.
administrativeUnitLevel
chosen
Indicates the hierarchical level or rank of an administrative unit within an overall administrative or governmental structure.
-
D.
authorizationLevel
Indicates the degree or tier of access rights or permissions granted to an entity within a system or context.
-
E.
subjectAreaLevel
Indicates the hierarchical level or depth of specialization of a particular subject area in relation to others.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820b9c808190b6f9201e4b2e85c2 |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:59 p.m.