Triple
T30169372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larak |
E766875
|
entity |
| Predicate | possibleCultCenterOf |
P114792
|
FINISHED |
| Object | Pabilsag |
—
|
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: Pabilsag | Statement: [Larak, possibleCultCenterOf, Pabilsag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleCultCenterOf Context triple: [Larak, possibleCultCenterOf, Pabilsag]
-
A.
hasCulticCenter
Indicates that an entity serves as the primary religious or ritual center associated with another entity.
-
B.
associatedWithCultCenter
Indicates a relationship where something (such as a deity, object, or practice) is linked to, connected with, or primarily related to a specific cult center or place of worship.
-
C.
hasCultPlaceType
Indicates that an entity is associated with a place used for cultic or religious activities of a specified type.
-
D.
centerOfCultFrom
chosen
Indicates that a location serves as the primary cult center or focal place of worship originating from a particular source or entity.
-
E.
typeOfCult
Indicates that one entity is a specific kind or category of cult relative to 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 7:24 p.m.