Triple
T19812244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halahala poison |
E475974
|
entity |
| Predicate | purposeOfConsumption |
P21011
|
FINISHED |
| Object | to protect the universe |
—
|
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: to protect the universe | Statement: [Halahala poison, purposeOfConsumption, to protect the universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfConsumption Context triple: [Halahala poison, purposeOfConsumption, to protect the universe]
-
A.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
B.
reasonForUse
chosen
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
C.
purposeOfConstruction
Indicates that one entity was constructed or built in order to serve, enable, or fulfill the function, goal, or intended use represented by another entity.
-
D.
traditionalPurpose
Indicates that something serves a role, function, or use that is established by long-standing custom or tradition.
-
E.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6542c9c5c81908772e88caa067e63 |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.