Triple
T35965354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taketomi, Okinawa |
E1040127
|
entity |
| Predicate | hasTraditionalRoofStyle |
P78546
|
FINISHED |
| Object | red clay roof tiles with shisa statues |
—
|
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: red clay roof tiles with shisa statues | Statement: [Taketomi, Okinawa, hasTraditionalRoofStyle, red clay roof tiles with shisa statues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalRoofStyle Context triple: [Taketomi, Okinawa, hasTraditionalRoofStyle, red clay roof tiles with shisa statues]
-
A.
hasTraditionalHouseStyle
Indicates that an entity possesses or is characterized by a traditional style of house or residential architecture.
-
B.
hasTypeOfRoof
chosen
Indicates that an entity possesses or is characterized by a specific kind or style of roof.
-
C.
hasRoofShape
Indicates that one entity possesses or is characterized by a specific shape or form of roof.
-
D.
hasIconicRoofShape
Indicates that an entity possesses a roof with a distinctive, widely recognized, or characteristic shape.
-
E.
traditionallyHouses
Indicates that one entity has historically or customarily served as the location or container for another entity.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: May 3, 2026, 4:07 p.m.