Triple
T174711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Orlando Resort |
E3550
|
entity |
| Predicate | significantExpansion |
P1516
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Universal Orlando Resort, significantExpansion, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantExpansion Context triple: [Universal Orlando Resort, significantExpansion, 1999]
-
A.
expandedDuring
Indicates that an entity increased in size, scope, or extent over the course of a specified time period or event.
-
B.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
C.
expandedSignificantlyInYear
chosen
Indicates that an entity underwent a substantial increase or growth during a specified year.
-
D.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
-
E.
collapsedDuring
Indicates that one entity structurally failed or fell down while another specified event or process was occurring.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e32da88190ad9485aecd0bf08f |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a256689f908190afeb5ee82022a911 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.