Triple
T26283636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Bougainville |
E661070
|
entity |
| Predicate | upeHeaddressRepresents |
P119013
|
FINISHED |
| Object | initiation and manhood |
—
|
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: initiation and manhood | Statement: [Flag of Bougainville, upeHeaddressRepresents, initiation and manhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upeHeaddressRepresents Context triple: [Flag of Bougainville, upeHeaddressRepresents, initiation and manhood]
-
A.
obverseHeaddressType
Indicates the type or style of headdress depicted on the obverse (front) side of an object, typically a coin or medal.
-
B.
headdressType
chosen
Indicates the specific kind or category of headdress associated with an entity.
-
C.
hasTraditionalHeaddressHeight
Indicates the relationship between an entity and the measured height of its traditional headdress.
-
D.
traditionalHeaddress
Indicates that an entity wears or is associated with a culturally traditional headdress as part of customary or ceremonial attire.
-
E.
headAttachment
Indicates that one entity is physically or structurally attached to the head or top part of 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e7593c881908faeda8a64f3e246 |
completed | May 2, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:02 p.m.