Triple
T35470363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covenant invasion of New Mombasa |
E1025190
|
entity |
| Predicate | involvesUnitType |
P1063
|
FINISHED |
| Object | ODST squad |
—
|
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: ODST squad | Statement: [Covenant invasion of New Mombasa, involvesUnitType, ODST squad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesUnitType Context triple: [Covenant invasion of New Mombasa, involvesUnitType, ODST squad]
-
A.
involvedUnit
chosen
Indicates that a particular unit (such as a group, organization, or division) participates in, is associated with, or plays a role in the referenced event or activity.
-
B.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
C.
mayIncludeUnitType
Indicates that something is allowed to contain or be associated with a particular type of unit.
-
D.
hasUnitIn
Indicates that one entity is contained or measured within another as a unit, specifying a unit-of-measure or component relationship.
-
E.
isUnitIn
Indicates that a specific unit is located within or belongs to a particular container, group, or context.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:04 p.m.