Triple
T1624190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonardo Hotels |
E35099
|
entity |
| Predicate | corporateFocus |
P18486
|
FINISHED |
| Object | meetings and events |
—
|
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: meetings and events | Statement: [Leonardo Hotels, corporateFocus, meetings and events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporateFocus Context triple: [Leonardo Hotels, corporateFocus, meetings and events]
-
A.
underlyingCompanyBusinessFocus
Indicates the primary industry, sector, or type of business activity that the underlying company is focused on.
-
B.
corporateTransformation
Indicates a relationship where an organization undergoes a significant structural, strategic, or operational change from one corporate state to another.
-
C.
brandFocus
chosen
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
D.
company
Indicates that an entity is a business organization engaged in commercial, industrial, or professional activities.
-
E.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.