Triple
T28109254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alitagtag |
E710443
|
entity |
| Predicate | hasNotableDevotion |
P146509
|
FINISHED |
| Object | Holy Cross of Alitagtag |
—
|
NE NERFINISHED |
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: Holy Cross of Alitagtag | Statement: [Alitagtag, hasNotableDevotion, Holy Cross of Alitagtag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDevotion Context triple: [Alitagtag, hasNotableDevotion, Holy Cross of Alitagtag]
-
A.
hasDevotionalRole
Indicates that an entity holds or performs a specific role or function within a devotional or religious practice.
-
B.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
C.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
D.
hasDevotionalFollowing
chosen
Indicates that an entity is admired, revered, or followed with strong devotion or loyalty by a group of people.
-
E.
hasSignificanceForDeity
Indicates that something holds particular importance, value, or meaning in relation to a specific deity.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: April 27, 2026, 9:10 p.m.