Triple
T31951250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lafkenche people |
E815783
|
entity |
| Predicate | spiritualRelationshipWith |
P80684
|
FINISHED |
| Object | sea |
—
|
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: sea | Statement: [Lafkenche people, spiritualRelationshipWith, sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualRelationshipWith Context triple: [Lafkenche people, spiritualRelationshipWith, sea]
-
A.
spiritualConnectionTo
chosen
Indicates a non-physical, often transcendent or faith-based bond or relationship that exists between two entities.
-
B.
devotionalRelationship
Indicates a relationship in which one entity expresses deep religious or spiritual devotion, reverence, or worship toward another entity.
-
C.
spiritualMeans
Indicates that one entity serves as a spiritual method, medium, or pathway through which another entity attains or engages in a spiritual state, goal, or practice.
-
D.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
E.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2a9fadc8190a3b5a5afdbdc82aa |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:07 a.m.