Triple
T94105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Tradition |
E1891
|
entity |
| Predicate | isComplementaryTo |
P162
|
FINISHED |
| Object | Sacred Scripture |
—
|
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: Sacred Scripture | Statement: [Holy Tradition, isComplementaryTo, Sacred Scripture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isComplementaryTo Context triple: [Holy Tradition, isComplementaryTo, Sacred Scripture]
-
A.
complements
chosen
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
B.
competesWith
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
E.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a2512ef600819084d3c627f0d534f4 |
completed | Feb. 28, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69a24eb9a5ac8190b1d1300e8c4e3606 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.