Triple
T6152130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cable Street |
E137227
|
entity |
| Predicate | hasEstimatedAttendance |
P3846
|
FINISHED |
| Object | tens of thousands of people |
—
|
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: tens of thousands of people | Statement: [Battle of Cable Street, hasEstimatedAttendance, tens of thousands of people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstimatedAttendance Context triple: [Battle of Cable Street, hasEstimatedAttendance, tens of thousands of people]
-
A.
fanAttendance
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
-
B.
approximateAudienceSize
chosen
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
C.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
-
D.
attendanceAnnounced
Indicates that an official statement has been made about whether and/or how many people will attend an event.
-
E.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cfe20408190b5ec9b987e1a4206 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.