Triple
T22413445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In a Crowd of Thousands |
E554048
|
entity |
| Predicate | recallsEvent |
P12313
|
FINISHED |
| Object | royal family public appearance |
—
|
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: royal family public appearance | Statement: [In a Crowd of Thousands, recallsEvent, royal family public appearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recallsEvent Context triple: [In a Crowd of Thousands, recallsEvent, royal family public appearance]
-
A.
recalledIn
chosen
Indicates that an entity is mentioned, remembered, or brought up again within a specific context, such as a document, conversation, or event.
-
B.
safetyRecall
Indicates that a product has been officially recalled due to identified safety issues or hazards.
-
C.
recalledBy
Indicates that an entity is brought back, retrieved, or remembered as a result of another entity’s action or prompting.
-
D.
causeOfRecall
Indicates that something is the reason or factor that led to a product or item being recalled.
-
E.
recalledFromOffice
Indicates that an entity has been officially summoned or brought back from its office or post, typically ending or interrupting its assignment 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1594496348190ba25dc0193d092f2 |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.