Triple
T2200248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eye of Providence |
E50470
|
entity |
| Predicate | hasEarlierPrecedent |
P3444
|
FINISHED |
| Object | Christian Trinity symbolism |
—
|
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: Christian Trinity symbolism | Statement: [Eye of Providence, hasEarlierPrecedent, Christian Trinity symbolism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierPrecedent Context triple: [Eye of Providence, hasEarlierPrecedent, Christian Trinity symbolism]
-
A.
hasCourtPrecedence
Indicates that one court decision or ruling holds authoritative priority over another in legal reasoning or application.
-
B.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
C.
hasHistoricalPrecursor
chosen
Indicates that one entity existed earlier and served as a predecessor, model, or influential forerunner to the other in a historical context.
-
D.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
E.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa06bb4819092d7021358846e5f |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.