Triple
T928072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian Revolution of 2011 |
E20028
|
entity |
| Predicate | arrestsApproximate |
P13732
|
FINISHED |
| Object | thousands |
—
|
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: thousands | Statement: [Egyptian Revolution of 2011, arrestsApproximate, thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrestsApproximate Context triple: [Egyptian Revolution of 2011, arrestsApproximate, thousands]
-
A.
arrestedFor
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
B.
numberOfPrisonersApproximate
chosen
Indicates an approximate count of prisoners associated with an entity or situation, rather than an exact number.
-
C.
estimatedPrisonerCount
Indicates the estimated number of prisoners associated with a particular context, such as a location, time period, or event.
-
D.
attemptedArrestBy
Indicates that one entity tried, but may not have succeeded, to place another entity under arrest.
-
E.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b32de3cc81908a0ef885795677ff |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b29876348190a29f4ff9878074a5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.