Triple
T30927940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forum of Pompeii |
E787907
|
entity |
| Predicate | mainAxisOrientation |
P12663
|
FINISHED |
| Object | north–south |
—
|
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: north–south | Statement: [Forum of Pompeii, mainAxisOrientation, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAxisOrientation Context triple: [Forum of Pompeii, mainAxisOrientation, north–south]
-
A.
hasOrientation
chosen
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
B.
primaryAxisUnits
Indicates the units of measurement used along the primary axis in a coordinate system, chart, or spatial reference.
-
C.
styleOrientation
Indicates the general stylistic direction or aesthetic approach that characterizes how something is designed, presented, or expressed.
-
D.
isAxisDirection
Indicates that one direction is aligned with or corresponds to a principal axis (such as x, y, or z) in a given coordinate system.
-
E.
valueOrientation
Indicates how an entity’s preferences, priorities, or attitudes are directed toward particular values or value systems.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 8:51 p.m.