Triple
T111723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Native American Church |
E2261
|
entity |
| Predicate | ceremonyLeaderTitle |
P2097
|
FINISHED |
| Object | roadman |
—
|
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: roadman | Statement: [Native American Church, ceremonyLeaderTitle, roadman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyLeaderTitle Context triple: [Native American Church, ceremonyLeaderTitle, roadman]
-
A.
ceremonialRole
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
B.
ceremonyType
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
C.
civilianLeaderTitle
Indicates the official title held by a person who serves as the civilian leader of a group, organization, or jurisdiction.
-
D.
honorificTitle
chosen
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
E.
leadershipPosition
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.