Triple
T35502006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States privateers |
E1026033
|
entity |
| Predicate | notablePortOfOrigin |
P93271
|
FINISHED |
| Object | Baltimore |
E13094
|
NE 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: Baltimore | Statement: [United States privateers, notablePortOfOrigin, Baltimore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePortOfOrigin Context triple: [United States privateers, notablePortOfOrigin, Baltimore]
-
A.
capitalOfOrigin
Indicates that one entity is the capital city associated with the origin (such as birthplace, founding place, or source location) of another entity.
-
B.
portOfOrigin
chosen
Indicates the location from which something (such as a shipment or vessel) originally departs or is first sent.
-
C.
denominationOfOrigin
Indicates a legally recognized origin relationship where a product’s quality or characteristics are specifically attributable to being produced in a particular geographic region.
-
D.
notableNationality
Indicates that an entity is notably associated with a particular nationality, often by origin, citizenship, or cultural identity.
-
E.
notableInRegion
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
- F. None of above.
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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384a2e8c7481908b0cea5b00a6e057 |
completed | June 21, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.