Triple
T34769899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOEX Offshore 2007 |
E1002334
|
entity |
| Predicate | legalStatusInSpill |
P121935
|
FINISHED |
| Object | defendant in civil litigation |
—
|
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: defendant in civil litigation | Statement: [MOEX Offshore 2007, legalStatusInSpill, defendant in civil litigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInSpill Context triple: [MOEX Offshore 2007, legalStatusInSpill, defendant in civil litigation]
-
A.
legalStatusOfSalvage
Indicates the legal classification or validity of a salvage operation or salvaged property under applicable laws.
-
B.
legalStatusAfterEvent
chosen
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
-
C.
legalStatusEvent
Indicates an event or action that changes, establishes, or affects the legal status or standing of an entity.
-
D.
registrationStatusAfterAccident
Indicates the state of an entity’s registration following the occurrence of an accident.
-
E.
wreckStatus
Indicates the condition or state of damage of an object, typically describing whether and how badly it has been wrecked.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 3, 2026, 3:59 p.m.