Triple
T2931599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Collins |
E78966
|
entity |
| Predicate | eventContext |
P44016
|
FINISHED |
| Object | Anglo-Irish Treaty signed in London on 6 December 1921 |
—
|
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: Anglo-Irish Treaty signed in London on 6 December 1921 | Statement: [Michael Collins, eventContext, Anglo-Irish Treaty signed in London on 6 December 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventContext Context triple: [Michael Collins, eventContext, Anglo-Irish Treaty signed in London on 6 December 1921]
-
A.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
-
C.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
D.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
E.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
- F. None of above. chosen
Provenance (4 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad980368e48190a50b59917af4786a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:55 p.m.