Triple
T11324217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action off Samar |
E268167
|
entity |
| Predicate | U.S.shipTypeInvolved |
P8971
|
FINISHED |
| Object | escort carrier |
—
|
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: escort carrier | Statement: [Action off Samar, U.S.shipTypeInvolved, escort carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: U.S.shipTypeInvolved Context triple: [Action off Samar, U.S.shipTypeInvolved, escort carrier]
-
A.
involvedShipUnitedStates
Indicates that a ship involved in an event, action, or relationship is associated with or belongs to the United States.
-
B.
shipTypeInvolved
chosen
Indicates that a particular type or class of ship is involved or participates in a specified event, situation, or relationship.
-
C.
numberOfShipsInvolved
Indicates the total count of ships that participated or were involved in a specified event or situation.
-
D.
aircraftCarrierInvolved
Indicates that an aircraft carrier participates in, is present at, or is otherwise directly involved in the specified event or situation.
-
E.
shipInvolved
Indicates that a ship participates in, is associated with, or plays a role in a specified event or situation.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e122e48190b3f890de8d561480 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.