Triple
T38156927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile World Congress 2015 |
E952910
|
entity |
| Predicate | exhibitorsApprox |
P143910
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Mobile World Congress 2015, exhibitorsApprox, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhibitorsApprox Context triple: [Mobile World Congress 2015, exhibitorsApprox, 2000]
-
A.
exhibitorsFrom
Indicates a relationship where certain exhibitors originate from, are associated with, or come from a specified source, location, or organization.
-
B.
exhibitorsNumber
chosen
Indicates the total count of exhibitors associated with a given event or exhibition.
-
C.
hasExhibitors
Indicates that an entity includes, hosts, or is associated with one or more exhibitors.
-
D.
exhibitorType
Indicates the specific role or category an exhibitor belongs to within an exhibition or event context.
-
E.
exhibitFor
Indicates a relationship where something is displayed, presented, or shown for the benefit, use, or consideration of a particular audience, purpose, or 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.