Triple
T25277074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Reserve Fleet |
E633729
|
entity |
| Predicate | maintainedStatusOfShips |
P130838
|
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: [Atlantic Reserve Fleet, maintainedStatusOfShips, inactive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedStatusOfShips Context triple: [Atlantic Reserve Fleet, maintainedStatusOfShips, inactive]
-
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.
workStatus_OnTheCatalogueOfShips
Indicates that a work’s status is determined by whether it appears in the Catalogue of Ships section of the text.
-
C.
dispositionOfShips
Indicates the arrangement, allocation, or positioning of ships relative to a plan, location, or situation.
-
D.
numberOfShips
Indicates the quantity of ships associated with a given entity or situation.
-
E.
navyListStatus
chosen
Indicates the status or classification of an entity within a navy’s official list or registry.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba6eb208190823b251f5888044a |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:18 p.m.