Triple
T21423807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consumer Electronics Show |
E528501
|
entity |
| Predicate | typicalAttendeesNumber |
P111137
|
FINISHED |
| Object | over 150000 |
—
|
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: over 150000 | Statement: [Consumer Electronics Show, typicalAttendeesNumber, over 150000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAttendeesNumber Context triple: [Consumer Electronics Show, typicalAttendeesNumber, over 150000]
-
A.
guestCountApproximate
Indicates that the number of guests involved is represented as an estimated or approximate count rather than an exact figure.
-
B.
typicalGroupSize
Indicates the usual or characteristic number of individuals that typically form a group in this context.
-
C.
hasApproximateNumberOfPeople
chosen
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
-
D.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
E.
typicalGroupSizeRange
Indicates the usual minimum and maximum number of individuals that typically occur together in a group for the given entity.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8139ce848190b812d6d07f1bdef8 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.