Triple
T27800067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geku (Outer Shrine) |
E702214
|
entity |
| Predicate | hasOuterPrecinct |
P170385
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Geku (Outer Shrine), hasOuterPrecinct, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOuterPrecinct Context triple: [Geku (Outer Shrine), hasOuterPrecinct, yes]
-
A.
hasInnerPrecinct
Indicates that one area, structure, or zone contains another, more central or enclosed precinct within its boundaries.
-
B.
hasNearbyPrecinct
Indicates that one location has a police precinct or similar administrative station situated close to it in geographic proximity.
-
C.
isMajorPrecinctFor
Indicates that one entity serves as the primary or main precinct responsible for another entity within a given jurisdiction or context.
-
D.
hasNumberedPrecinct
Indicates that an entity is associated with a specific precinct identified by a number.
-
E.
partOfPrecinct
Indicates that one entity is a subdivision or component contained within a specific precinct.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 5:33 p.m.