Triple
T36854320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YLIS |
E910752
|
entity |
| Predicate | hasLocalCouncilArea |
P200075
|
FINISHED |
| Object | City of Lismore |
—
|
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: City of Lismore | Statement: [YLIS, hasLocalCouncilArea, City of Lismore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalCouncilArea Context triple: [YLIS, hasLocalCouncilArea, City of Lismore]
-
A.
hasLocalDistrict
Indicates that an entity is associated with or falls under the jurisdiction of a specific local administrative district.
-
B.
hasTypeLocalGovernmentDistrict
Indicates that an entity is classified as a local government district within an administrative or governmental hierarchy.
-
C.
hasLocalCouncilRepresentation
Indicates that an entity is represented by a local council or has elected representatives serving on a local council.
-
D.
hasLocalGovernmentAreaCode
Indicates that an entity is associated with a specific local government area identified by a particular code.
-
E.
containsLocalAuthorityArea
Indicates that one entity geographically encompasses or includes the entire area governed by a specific local authority.
- F. None of above. chosen
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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69ff6fb9691c819082ee2f3c648b7dc1 |
completed | May 9, 2026, 5:32 p.m. |
Created at: May 3, 2026, 4:13 p.m.