Triple
T23706063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Drive, Orlando |
E585722
|
entity |
| Predicate | hasNumerous |
P62241
|
FINISHED |
| Object | mid-range hotels |
—
|
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: mid-range hotels | Statement: [International Drive, Orlando, hasNumerous, mid-range hotels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumerous Context triple: [International Drive, Orlando, hasNumerous, mid-range hotels]
-
A.
hasPlurality
Indicates that an entity or concept exists or is expressed in a plural form rather than a singular one.
-
B.
hasMultiple
chosen
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
C.
heldMany
Indicates that one entity has possessed or maintained control over a large number or quantity of another entity over time.
-
D.
hasNotableNumber
Indicates that an entity is associated with a specific number that is considered significant, distinctive, or noteworthy in some context.
-
E.
manyMembersAre
Indicates that a large number of members within a group possess a specified property or participate in a particular role or condition.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b687ae708190a9233100a9e0204f |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.