Triple
T3833699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panama–Pacific International Exposition |
E91075
|
entity |
| Predicate | featuredEventType |
P7504
|
FINISHED |
| Object | industrial exhibitions |
—
|
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: industrial exhibitions | Statement: [Panama–Pacific International Exposition, featuredEventType, industrial exhibitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredEventType Context triple: [Panama–Pacific International Exposition, featuredEventType, industrial exhibitions]
-
A.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
B.
typeOfEvent
chosen
Indicates that one entity is classified as a specific kind or category of event.
-
C.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
-
D.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
E.
eventEdition
Indicates a specific version or iteration of an event within a recurring or multi-edition series.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb88b8a8819082d4bdbc5bc45366 |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.