Triple
T4544492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | January 25 Uprising |
E110013
|
entity |
| Predicate | usedCommunicationTool |
P33439
|
FINISHED |
| Object | social media |
—
|
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: social media | Statement: [January 25 Uprising, usedCommunicationTool, social media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCommunicationTool Context triple: [January 25 Uprising, usedCommunicationTool, social media]
-
A.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or entity.
-
B.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
C.
usesToolType
chosen
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
D.
usedInDigitalCommunication
Indicates that something is employed as a medium, tool, or element within digital or electronic communication processes.
-
E.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d62a8481909d5d803a582c76a1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.