Triple
T3344482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Ostia (Portus Traiani) |
E70336
|
entity |
| Predicate | builtEnvironment |
P47347
|
FINISHED |
| Object | massive masonry quays |
—
|
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: massive masonry quays | Statement: [Port of Ostia (Portus Traiani), builtEnvironment, massive masonry quays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtEnvironment Context triple: [Port of Ostia (Portus Traiani), builtEnvironment, massive masonry quays]
-
A.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
B.
builtNear
Indicates that one entity was constructed at a location geographically close to another entity.
-
C.
buildingSystem
Indicates that one entity functions as a system, subsystem, or organized set of components that serves or supports the operation of a building.
-
D.
buildingCondition
Indicates the physical state or quality of a building, such as how well it is preserved, maintained, or structurally sound.
-
E.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f23008819084ea68b8431c50ab |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.