Triple
T7301976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River Reserve Fleet |
E167878
|
entity |
| Predicate | dispositionOfShips |
P76088
|
FINISHED |
| Object | scrapped |
—
|
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: scrapped | Statement: [Hudson River Reserve Fleet, dispositionOfShips, scrapped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dispositionOfShips Context triple: [Hudson River Reserve Fleet, dispositionOfShips, scrapped]
-
A.
statusOfOtherShips
Indicates the relationship that reports or reflects the current conditions or states (such as position, readiness, or operational status) of other ships.
-
B.
numberOfShips
Indicates the quantity of ships associated with a given entity or situation.
-
C.
numberOfShipsInvolved
Indicates the total count of ships that participated or were involved in a specified event or situation.
-
D.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
E.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
- F. None of above. chosen
Provenance (4 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb09164819099c4479d48c1688a |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb2d4c0c8190b4cc6fdfdb7f4827 |
completed | March 27, 2026, 8:40 p.m. |
Created at: March 27, 2026, 3:01 p.m.