Triple
T26699273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAIC-M / Acero-class fast attack interdiction craft |
E673105
|
entity |
| Predicate | isPatrolVessel |
P149073
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [FAIC-M / Acero-class fast attack interdiction craft, isPatrolVessel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPatrolVessel Context triple: [FAIC-M / Acero-class fast attack interdiction craft, isPatrolVessel, true]
-
A.
governmentVessel
Indicates that the vessel is owned, operated, or officially designated for use by a government or governmental authority.
-
B.
typeOfVesselEscorted
Indicates the specific kind of vessel that is being accompanied or protected in an escorting relationship.
-
C.
vesselRoleIdentified
chosen
Indicates that the specific functional role or purpose of a vessel within a context (e.g., a system, process, or operation) has been determined and recorded.
-
D.
flagStateOfOneVessel
Indicates that one vessel is flying or registered under the national flag (state) of another vessel.
-
E.
flagStateOfOtherVessel
Indicates the national flag or registry state under which another vessel is operating.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6177e2870819092bd441b95a21223 |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:30 a.m.