Triple
T13202529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignudi |
E314275
|
entity |
| Predicate | positionedAround |
P73004
|
FINISHED |
| Object | Old Testament narrative scenes |
—
|
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: Old Testament narrative scenes | Statement: [Ignudi, positionedAround, Old Testament narrative scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionedAround Context triple: [Ignudi, positionedAround, Old Testament narrative scenes]
-
A.
formsAround
Indicates that one entity develops or shapes itself so as to encircle, surround, or be organized around another entity.
-
B.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
C.
setAround
chosen
Indicates that one entity is positioned or arranged surrounding another entity or a central point.
-
D.
positionOnEnvironment
Indicates the spatial placement or location of an entity relative to a surrounding environment or surface.
-
E.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.