Triple
T36648730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archangels |
E904780
|
entity |
| Predicate | numberInSomeChristianTraditions |
P118449
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Archangels, numberInSomeChristianTraditions, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInSomeChristianTraditions Context triple: [Archangels, numberInSomeChristianTraditions, 7]
-
A.
usedInChristianTradition
Indicates that something is employed, practiced, or recognized within Christian religious beliefs, rituals, or cultural traditions.
-
B.
inChristianizedTradition
Indicates that something is understood, practiced, or represented within the context of Christianized religious or cultural tradition.
-
C.
definesNumberOfNaturesOfChrist
Indicates that an entity specifies or determines how many distinct natures Christ possesses.
-
D.
numberTradition
chosen
Indicates a relationship where a specific number is associated with, or holds significance within, a particular tradition or customary practice.
-
E.
languageOfScripturalTradition
Indicates the language in which a given scriptural or religious textual tradition is expressed or transmitted.
- 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.