Triple
T11353727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Galatea (71) |
E268898
|
entity |
| Predicate | locationRelativeToLand |
P16235
|
FINISHED |
| Object | off Alexandria, Egypt |
—
|
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: off Alexandria, Egypt | Statement: [HMS Galatea (71), locationRelativeToLand, off Alexandria, Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToLand Context triple: [HMS Galatea (71), locationRelativeToLand, off Alexandria, Egypt]
-
A.
positionRelativeToCoast
chosen
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
B.
positionRelativeToEarth
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
-
C.
locationRelativeToPitch
Indicates the spatial position of an entity in relation to the pitch (e.g., above, beside, or within the pitch area).
-
D.
locatedOnTerrain
Indicates that one entity is physically situated on or atop a particular terrain surface.
-
E.
locationGroundSegment
Indicates that one entity is located at or associated with a specific ground segment or ground-based infrastructure.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.