Triple
T34024725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seelands |
E872475
|
entity |
| Predicate | isInClarenceValleyRegion |
P178673
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Seelands, isInClarenceValleyRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInClarenceValleyRegion Context triple: [Seelands, isInClarenceValleyRegion, true]
-
A.
isInSouthernTablelands
Indicates that one entity is located within the Southern Tablelands region in relation to another or to a defined geographic area.
-
B.
locatedInRegionalDistrict
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
-
C.
isEasternSuburbOf
Indicates that one place is a suburb located to the east of another place.
-
D.
isCommercialSuburbOf
Indicates that one area functions primarily as a business or commercial district that is part of, or subordinate to, a larger urban area or city.
-
E.
containsRegionalCouncil
Indicates that one administrative or geographic entity includes a regional council within its jurisdiction or boundaries.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f713bfdc148190a249a7874320bab8 |
completed | May 3, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f7135fa2988190a20a94cfe616d754 |
completed | May 3, 2026, 9:20 a.m. |
Created at: May 1, 2026, 1:51 a.m.