Triple
T35573281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bithynians |
E1028001
|
entity |
| Predicate | coastalSea |
P72075
|
FINISHED |
| Object | Propontis |
—
|
NE NERFINISHED |
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: Propontis | Statement: [Bithynians, coastalSea, Propontis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalSea Context triple: [Bithynians, coastalSea, Propontis]
-
A.
seaType
Indicates the specific classification or category of a sea associated with an entity.
-
B.
seaOf
Indicates a relationship where one entity is metaphorically or literally surrounded or filled by another like a vast sea, emphasizing overwhelming abundance or expansiveness.
-
C.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
-
D.
primarySea
Indicates that one entity is the main or principal sea associated with another entity (such as a place, route, or feature).
-
E.
touchesSea
chosen
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.