Triple
T37257921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barfleur |
E924181
|
entity |
| Predicate | wasImportantMedievalHarbor |
P62857
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Barfleur, wasImportantMedievalHarbor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasImportantMedievalHarbor Context triple: [Barfleur, wasImportantMedievalHarbor, true]
-
A.
wasFirstMajorSeaportOf
Indicates that one place served as the earliest significant seaport for another place or region.
-
B.
isMainHarbourOf
Indicates that a harbour serves as the primary or principal port facility for a specified location or region.
-
C.
wasImportantCityOf
Indicates that a city held significant importance or prominence within a specified larger political or geographic entity during a given time period.
-
D.
isHistoricPortOf
chosen
Indicates that a location served as a significant port for another place during a past historical period.
-
E.
isHistoricCoastalCity
Indicates that a city is both historically significant and located along a coast.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.