Triple
T3344463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Ostia (Portus Traiani) |
E70336
|
entity |
| Predicate | primaryImports |
P47346
|
FINISHED |
| Object | grain from Egypt |
—
|
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: grain from Egypt | Statement: [Port of Ostia (Portus Traiani), primaryImports, grain from Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryImports Context triple: [Port of Ostia (Portus Traiani), primaryImports, grain from Egypt]
-
A.
primaryInput
Indicates that an entity serves as the main or principal input to a process, system, or operation.
-
B.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
C.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
D.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
E.
primaryProduct
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
- 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.