Triple
T2947721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M/V LeConte |
E79541
|
entity |
| Predicate | statusAfterIncident |
P13710
|
FINISHED |
| Object | refloated and repaired after 2004 grounding |
—
|
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: refloated and repaired after 2004 grounding | Statement: [M/V LeConte, statusAfterIncident, refloated and repaired after 2004 grounding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterIncident Context triple: [M/V LeConte, statusAfterIncident, refloated and repaired after 2004 grounding]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
handledAftermathOf
Indicates that one entity took responsibility for dealing with the consequences or fallout that occurred after another entity’s actions or events.
-
C.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
D.
aftermathPolicy
Indicates the policy, rules, or procedures that apply in the aftermath or consequences of a particular event or action.
-
E.
statusAfter2020
Indicates the condition or state of an entity as it exists after the year 2020.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b5916c8190b1163bf0b7fa136a |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.