Triple
T32028682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | near Seven Stones reef |
E817888
|
entity |
| Predicate | marineTraffic |
P49505
|
FINISHED |
| Object | busy shipping route |
—
|
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: busy shipping route | Statement: [near Seven Stones reef, marineTraffic, busy shipping route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marineTraffic Context triple: [near Seven Stones reef, marineTraffic, busy shipping route]
-
A.
fleetFocus
Indicates that attention, resources, or strategic priority are being directed toward a particular fleet within a broader operational or organizational context.
-
B.
EnglishFleetBase
Indicates a base or primary location associated with the English fleet in a given context.
-
C.
maritimeActivity
chosen
Indicates activities, operations, or behaviors that take place at sea or are directly related to maritime environments and navigation.
-
D.
shipRegistry
Indicates that an entity is officially recorded or listed in a particular ship registry or registration system.
-
E.
maritimeInfrastructure
Indicates the existence, presence, or involvement of facilities, structures, or systems that support maritime activities such as shipping, ports, and coastal operations between the related entities.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b46b78508190836c507d61961981 |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:17 a.m.