Triple
T5659705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nara City Hall |
E124704
|
entity |
| Predicate | locatedInRegionKnownFor |
P9687
|
FINISHED |
| Object | ancient temples |
—
|
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: ancient temples | Statement: [Nara City Hall, locatedInRegionKnownFor, ancient temples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInRegionKnownFor Context triple: [Nara City Hall, locatedInRegionKnownFor, ancient temples]
-
A.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
B.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
E.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
- 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:42 p.m.