Triple
T3898550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarchal cross |
E90430
|
entity |
| Predicate | hasVerticalElement |
P43274
|
FINISHED |
| Object | upright staff or shaft |
—
|
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: upright staff or shaft | Statement: [Patriarchal cross, hasVerticalElement, upright staff or shaft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerticalElement Context triple: [Patriarchal cross, hasVerticalElement, upright staff or shaft]
-
A.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
B.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
hasScroll
Indicates that an entity possesses, contains, or is associated with a scroll.
-
D.
hasExhibitElement
chosen
Indicates that something (such as an exhibit or display) includes or is composed of a particular element or component.
-
E.
hasLineElementForm
Indicates that something takes the form or representation of a line element within a given structure or context.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.