Triple
T9115307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Reliant (commandeered) |
E218705
|
entity |
| Predicate | operationalStatusAtEnd |
P86578
|
FINISHED |
| Object | heavily damaged |
—
|
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: heavily damaged | Statement: [USS Reliant (commandeered), operationalStatusAtEnd, heavily damaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalStatusAtEnd Context triple: [USS Reliant (commandeered), operationalStatusAtEnd, heavily damaged]
-
A.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
B.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
-
C.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
D.
operatedUntil
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
E.
endOfSeriesStatus
Indicates that a series, sequence, or collection has reached its final state or completion status.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a1340881909dc791b825e87ef2 |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:16 p.m.