Triple
T21715623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JA12 |
E536019
|
entity |
| Predicate | associatedWithWard |
P14475
|
FINISHED |
| Object | Toshima |
—
|
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: Toshima | Statement: [JA12, associatedWithWard, Toshima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWard Context triple: [JA12, associatedWithWard, Toshima]
-
A.
containsWard
chosen
Indicates that one entity includes, encompasses, or has within it a ward (such as a district, division, or dependent person) as part of its scope or responsibility.
-
B.
isWardOf
Indicates that one entity is under the guardianship, protection, or legal care of another entity as their ward.
-
C.
hasNeighbouringWard
Indicates that one ward is directly adjacent to or borders another ward geographically.
-
D.
associatedWithIwi
Indicates a relationship in which an entity is connected or linked to a particular iwi (tribe), typically through affiliation, relevance, or involvement.
-
E.
associatedWithPractice
Indicates a relationship in which an entity is connected or linked to a particular practice, activity, or customary way of doing something.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb53761b48190954a46e8155a84f0 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.