Triple
T4351058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ho‘oponopono |
E98026
|
entity |
| Predicate | traditionallyLedBy |
P35853
|
FINISHED |
| Object | family elder |
—
|
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: family elder | Statement: [Ho‘oponopono, traditionallyLedBy, family elder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyLedBy Context triple: [Ho‘oponopono, traditionallyLedBy, family elder]
-
A.
hadLeadershipFrom
chosen
Indicates that one entity received leadership, guidance, or direction from another entity.
-
B.
traditionsMaintainedBy
Indicates that certain traditions are preserved, upheld, or continued in practice by a particular entity.
-
C.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
D.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
-
E.
seriesLeader
Indicates that one entity serves as the primary leader, head, or main responsible figure for a particular series involving 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a99788819080b13a20124e49a0 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.