Triple
T26481046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanna people |
E664684
|
entity |
| Predicate | notableCargoCult |
P198157
|
FINISHED |
| Object | John Frum movement |
—
|
NE NERFINISHED |
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: John Frum movement | Statement: [Tanna people, notableCargoCult, John Frum movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCargoCult Context triple: [Tanna people, notableCargoCult, John Frum movement]
-
A.
notableCargo
Indicates that an entity is known for carrying or having carried a particularly important, famous, or otherwise noteworthy cargo.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableProduct
Indicates that a product is especially significant, prominent, or well-known in relation to the associated entity.
-
D.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
E.
notablyBorneBy
Indicates that something is especially or prominently carried, supported, or borne by a particular entity, in a way that is distinctive or noteworthy.
- F. None of above. chosen
Provenance (4 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
| PDg | Predicate description generation | batch_69feced436a48190b761db7df2d6b6bd |
completed | May 9, 2026, 6:06 a.m. |
Created at: April 27, 2026, 12:27 a.m.