Triple
T16520922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decumani of Naples |
E401314
|
entity |
| Predicate | isAxisType |
P93347
|
FINISHED |
| Object | decumanus |
—
|
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: decumanus | Statement: [Decumani of Naples, isAxisType, decumanus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAxisType Context triple: [Decumani of Naples, isAxisType, decumanus]
-
A.
isAxisBetween
Indicates that one entity serves as a central or reference axis positioned between two other entities in a spatial or structural arrangement.
-
B.
isOnAxis
Indicates that one entity lies directly along a specified axis or reference line defined by another entity or coordinate system.
-
C.
axesType
chosen
Indicates the type or configuration of axes associated with an entity, such as their orientation, scale, or dimensional setup.
-
D.
usesAxis
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
-
E.
hasAxisCount
Indicates that an entity is associated with a specified number of axes.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e804e388190b684bde2c82ab770 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.