Triple
T7369040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astoria Reserve Fleet |
E169944
|
entity |
| Predicate | vesselStatus |
P70077
|
FINISHED |
| Object | inactive |
—
|
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: inactive | Statement: [Astoria Reserve Fleet, vesselStatus, inactive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vesselStatus Context triple: [Astoria Reserve Fleet, vesselStatus, inactive]
-
A.
hasVessel
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
-
B.
sailingStatus
chosen
Indicates the current operational state or condition of a vessel in relation to its sailing activity (e.g., underway, docked, anchored, or out of service).
-
C.
workStatus_OnTheCatalogueOfShips
Indicates that a work’s status is determined by whether it appears in the Catalogue of Ships section of the text.
-
D.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
E.
marineProtectionStatus
Indicates the level or type of legal or regulatory protection applied to a marine area or resource.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.