Triple
T32180259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Such a Full Sea |
E821959
|
entity |
| Predicate | laborSettlementName |
P106368
|
FINISHED |
| Object | B-Mor |
—
|
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: B-Mor | Statement: [On Such a Full Sea, laborSettlementName, B-Mor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laborSettlementName Context triple: [On Such a Full Sea, laborSettlementName, B-Mor]
-
A.
nativeTitleSettlement
Indicates that a legal settlement has been reached recognizing or resolving native or indigenous title rights to land or territory.
-
B.
hasSettlementName
chosen
Indicates that a settlement is associated with a specific name by which it is known.
-
C.
nativeTitleSettlementWith
Indicates a legal or formal settlement agreement concerning native or indigenous title rights between the related parties.
-
D.
settlementCity
Indicates that a settlement is located within or corresponds to a particular city.
-
E.
organizedSettlement
Indicates that an entity actively planned, coordinated, and arranged the establishment or occurrence of a settlement.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba7cbc708190ab91b828e5ef2976 |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:34 a.m.