Triple
T5004809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle off Carrickfergus |
E112463
|
entity |
| Predicate | shipTypeOnAmericanSide |
P8971
|
FINISHED |
| Object | sloop-of-war |
—
|
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: sloop-of-war | Statement: [Battle off Carrickfergus, shipTypeOnAmericanSide, sloop-of-war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipTypeOnAmericanSide Context triple: [Battle off Carrickfergus, shipTypeOnAmericanSide, sloop-of-war]
-
A.
involvedShipUnitedStates
Indicates that a ship involved in an event, action, or relationship is associated with or belongs to the United States.
-
B.
shipTypeProduced
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
C.
shipTypeInvolved
chosen
Indicates that a particular type or class of ship is involved or participates in a specified event, situation, or relationship.
-
D.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
E.
shipClass
Indicates the classification or type category to which a particular ship belongs.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.