Triple
T4200399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatican City flag |
E86050
|
entity |
| Predicate | keyOrientation |
P54320
|
FINISHED |
| Object | crossed |
—
|
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: crossed | Statement: [Vatican City flag, keyOrientation, crossed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOrientation Context triple: [Vatican City flag, keyOrientation, crossed]
-
A.
keyPosition
Indicates the specific location or placement of a key within a defined space or system.
-
B.
valueOrientation
Indicates how an entity’s preferences, priorities, or attitudes are directed toward particular values or value systems.
-
C.
keyTarget
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
-
D.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
-
E.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
- F. None of above. chosen
Provenance (4 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0363bbb8819093f396afe91972e2 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af02e4e2308190b527e3b78eb8fa71 |
completed | March 9, 2026, 5:27 p.m. |
Created at: March 9, 2026, 3:49 p.m.