Triple
T24787672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross of Alcoraz |
E620161
|
entity |
| Predicate | headPosition |
P98636
|
FINISHED |
| Object | in the four quarters of the cross |
—
|
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: in the four quarters of the cross | Statement: [Cross of Alcoraz, headPosition, in the four quarters of the cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headPosition Context triple: [Cross of Alcoraz, headPosition, in the four quarters of the cross]
-
A.
headLocation
Indicates the spatial position or place where an entity’s head is located.
-
B.
positionHead
Indicates that one entity serves as the head or primary governing element in the positional or syntactic structure of another entity.
-
C.
hasHeadPosition
chosen
Indicates the specific spatial position or orientation of an entity’s head relative to a reference frame or context.
-
D.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
E.
headbandPosition
Indicates the spatial placement or orientation of a headband relative to the head or face.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110071008190a430ca780b567fe4 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:46 a.m.