Triple
T2741824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palo Monte |
E60767
|
entity |
| Predicate | hasCorePractice |
P1188
|
FINISHED |
| Object | spirit veneration |
—
|
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: spirit veneration | Statement: [Palo Monte, hasCorePractice, spirit veneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorePractice Context triple: [Palo Monte, hasCorePractice, spirit veneration]
-
A.
hasImportantPractice
chosen
Indicates that an entity engages in or possesses a practice, activity, or procedure considered significant or essential within a given context.
-
B.
hasCoreFacility
Indicates that an entity possesses, hosts, or is equipped with a central, shared facility that supports key operations or services.
-
C.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
D.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
E.
hasPracticeIssue
Indicates that an entity is associated with a specific problem, concern, or challenge arising in practical or real-world practice.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb303898819098a7d192e29817f8 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.