Triple
T1719173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMB |
E37352
|
entity |
| Predicate | historicalPort |
P25415
|
FINISHED |
| Object | 139 |
—
|
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: 139 | Statement: [SMB, historicalPort, 139]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPort Context triple: [SMB, historicalPort, 139]
-
A.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
B.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
-
C.
hasRiverPortHistory
chosen
Indicates that an entity has a historical association with functioning as a river port or hosting river port activities.
-
D.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.