Triple
T25277071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Reserve Fleet |
E633729
|
entity |
| Predicate | hasAnchorageType |
P160110
|
FINISHED |
| Object | anchorage |
—
|
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: anchorage | Statement: [Atlantic Reserve Fleet, hasAnchorageType, anchorage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnchorageType Context triple: [Atlantic Reserve Fleet, hasAnchorageType, anchorage]
-
A.
hasAnchorageArea
Indicates that one entity provides or defines an area suitable for anchoring (e.g., for vessels) in relation to another entity.
-
B.
hasAnchorStores
Indicates that a retail property or shopping center includes one or more major anchor stores as primary tenants.
-
C.
anchoredBy
Indicates that one entity is fixed, secured, or held in place by another acting as its anchor.
-
D.
hasANC
Indicates that an entity has received or is associated with antenatal care (ANC) services.
-
E.
hasAnchorLocation
Indicates that one entity serves as the fixed reference or attachment point (anchor) for the location or position of another entity.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 21, 2026, 1:18 p.m.