Triple
T13347859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | golden shachihoko |
E318002
|
entity |
| Predicate | isTypicallyPlacedAt |
P91034
|
FINISHED |
| Object | ends of main roof ridge |
—
|
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: ends of main roof ridge | Statement: [golden shachihoko, isTypicallyPlacedAt, ends of main roof ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyPlacedAt Context triple: [golden shachihoko, isTypicallyPlacedAt, ends of main roof ridge]
-
A.
oftenLocatedAt
chosen
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
B.
meetsInPlaceOf
Indicates that one entity meets or comes together with another specifically at a designated place or location.
-
C.
typicalStorePlacement
Indicates the usual or standard physical location where an item is placed or displayed within a store.
-
D.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
E.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8b28e48190a23194e03a74b41b |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.