Triple
T38598432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Pavilion (Expo 86) |
E934144
|
entity |
| Predicate | targetedSector |
P52507
|
FINISHED |
| Object | tourism promotion |
—
|
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: tourism promotion | Statement: [United States Pavilion (Expo 86), targetedSector, tourism promotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedSector Context triple: [United States Pavilion (Expo 86), targetedSector, tourism promotion]
-
A.
targetsSector
chosen
Indicates that an entity is directed toward, focused on, or intended to affect a particular economic or industry sector.
-
B.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
C.
sectoralCoverage
Indicates the specific sectors, industries, or domains to which something (such as a policy, agreement, or dataset) applies or extends.
-
D.
typicalConstituentSector
Indicates that something is a usual or characteristic sector that forms part of a larger whole or system.
-
E.
notableSector
Indicates that an entity is particularly prominent, influential, or significant within a specified sector or industry.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 3, 2026, 4:32 p.m.