Triple
T14095002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fascio Littorio |
E339229
|
entity |
| Predicate | axePosition |
P112796
|
FINISHED |
| Object | protruding from the side of the rods |
—
|
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: protruding from the side of the rods | Statement: [Fascio Littorio, axePosition, protruding from the side of the rods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: axePosition Context triple: [Fascio Littorio, axePosition, protruding from the side of the rods]
-
A.
axeType
Indicates the specific kind or category of axe associated with an entity or action.
-
B.
axisObjective
Indicates that an entity serves as a primary goal, target, or focal objective along a defined axis or strategic direction in a given context.
-
C.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
-
D.
conePosition
Indicates the spatial position or placement of a cone relative to a reference frame or environment.
-
E.
coordinateAxis
Indicates that one entity serves as a reference axis or directional basis for positioning, measuring, or orienting another entity in a coordinate system.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb7fb3c819083266dbe7e93aaff |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.