Triple
T36493801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eparch |
E899121
|
entity |
| Predicate | hasPastoralSymbol |
P67846
|
FINISHED |
| Object | pastoral staff |
—
|
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: pastoral staff | Statement: [eparch, hasPastoralSymbol, pastoral staff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastoralSymbol Context triple: [eparch, hasPastoralSymbol, pastoral staff]
-
A.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
B.
haveOfficialSymbols
Indicates that an entity possesses formally recognized symbols (such as flags, emblems, or insignia) that officially represent it.
-
C.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
D.
hasLiturgicalSymbol
chosen
Indicates that one entity serves as a liturgical symbol or emblem associated with another entity within a religious or worship context.
-
E.
hasClanSymbol
Indicates that an entity is associated with a particular clan through a specific identifying symbol.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
Created at: May 3, 2026, 4:10 p.m.