Triple
T18334434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega Sector |
E439231
|
entity |
| Predicate | hasCoverForAgents |
P5998
|
FINISHED |
| Object | civilian occupations |
—
|
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: civilian occupations | Statement: [Omega Sector, hasCoverForAgents, civilian occupations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverForAgents Context triple: [Omega Sector, hasCoverForAgents, civilian occupations]
-
A.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
B.
hasCoverage
chosen
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
C.
hasAgent
Indicates that an action or event is carried out or initiated by a particular agent.
-
D.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
E.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecc91148190aa820fcd466009ce |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.