Triple
T8312178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venta Silurum |
E194614
|
entity |
| Predicate | wallCircuitShape |
P23857
|
FINISHED |
| Object | roughly rectangular |
—
|
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: roughly rectangular | Statement: [Venta Silurum, wallCircuitShape, roughly rectangular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wallCircuitShape Context triple: [Venta Silurum, wallCircuitShape, roughly rectangular]
-
A.
hasWallShape
chosen
Indicates that an entity possesses a wall whose form or outline matches a specified geometric or structural shape.
-
B.
wallFeature
Indicates that one entity functions as a structural or design feature associated with a wall of another entity.
-
C.
hasWallType
Indicates the specific kind or classification of wall associated with an entity.
-
D.
courtyardShape
Indicates the geometric form or configuration that characterizes a courtyard.
-
E.
wallMaterial
Indicates that one entity is the material from which a wall or walls of another entity are constructed.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f504ca8819087fb1f731f7a7cfd |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.