Triple
T18496396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | February 10, 2011 Mubarak speech |
E451958
|
entity |
| Predicate | mentioned |
P831
|
FINISHED |
| Object | martyrs of the protests |
—
|
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: martyrs of the protests | Statement: [February 10, 2011 Mubarak speech, mentioned, martyrs of the protests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentioned Context triple: [February 10, 2011 Mubarak speech, mentioned, martyrs of the protests]
-
A.
mentions
chosen
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
B.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
C.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
D.
mentionsSee
Indicates that one entity explicitly refers to or cites another entity within its content.
-
E.
mentionedButUnseen
Indicates that an entity is referred to or talked about within a context but does not actually appear or become directly observable there.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c09a8081909cf0b44df3682bb8 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.