Triple
T12953284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bontoc people |
E309945
|
entity |
| Predicate | traditionalHousingFeature |
P62698
|
FINISHED |
| Object | thatched roofs |
—
|
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: thatched roofs | Statement: [Bontoc people, traditionalHousingFeature, thatched roofs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHousingFeature Context triple: [Bontoc people, traditionalHousingFeature, thatched roofs]
-
A.
traditionalHomeOf
Indicates that a place is historically or customarily regarded as the primary homeland or origin location of a particular group or culture.
-
B.
traditionalHomeEnd
Indicates the point or time at which a traditional home, household, or customary domestic arrangement comes to an end.
-
C.
houseTraitAssociation
chosen
Indicates an associative relationship between a house and a particular trait or characteristic attributed to it.
-
D.
traditionalHomeStand
Indicates that an entity plays or hosts its home games at a venue considered its traditional or long-standing home location.
-
E.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:44 p.m.