Triple
T35313470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULTRA |
E1019840
|
entity |
| Predicate | wasConductedBy |
P30855
|
FINISHED |
| Object | Allies |
—
|
NE NERFINISHED |
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: Allies | Statement: [ULTRA, wasConductedBy, Allies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasConductedBy Context triple: [ULTRA, wasConductedBy, Allies]
-
A.
isConductedBy
chosen
Indicates that an event, activity, or process is carried out, organized, or overseen by a particular agent or entity.
-
B.
laterPerformedBy
Indicates that an action or event is carried out by a particular agent at a later time than another referenced action or event.
-
C.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
-
D.
wasConvenedBy
Indicates that an event, meeting, or gathering was formally called together, organized, or initiated by a specific agent or authority.
-
E.
performedUnder
Indicates that an action or task was carried out subject to, or within the scope of, a particular condition, authority, context, or framework.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.