Triple
T558887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eupatoria |
E13403
|
entity |
| Predicate | hasPortType |
P16380
|
FINISHED |
| Object | seaport |
—
|
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: seaport | Statement: [Eupatoria, hasPortType, seaport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortType Context triple: [Eupatoria, hasPortType, seaport]
-
A.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
-
B.
hasMajorPort
Indicates that a location possesses a primary, significant seaport used for major commercial or transportation activities.
-
C.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
D.
hasOutputType
Indicates that an entity produces, returns, or yields a result of a specified type.
-
E.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499df43f08190b514a38d36fc271d |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494bd78e8819083c519669158f209 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985952a481908b918350ececf484 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.