Triple
T16295316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orlando Venues |
E395630
|
entity |
| Predicate | ownedBy |
P347
|
FINISHED |
| Object | City of Orlando |
E11265
|
NE 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: City of Orlando | Statement: [Orlando Venues, ownedBy, City of Orlando]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Orlando Context triple: [Orlando Venues, ownedBy, City of Orlando]
-
A.
Orland
Orland is a small agricultural city in Northern California known for its farming community and rural character.
-
B.
Orlando
chosen
Orlando is a major city in central Florida known for its theme parks, tourism industry, and entertainment attractions.
-
C.
Orlando
Orlando is a common Italian surname borne by numerous individuals, including notable political and cultural figures.
-
D.
Orlando
Orlando is the Italian literary counterpart of the medieval knight Roland, best known as the chivalric hero of epic poems such as "Orlando Furioso."
-
E.
Orlando
Orlando is the middle name of William O. Butler, a 19th-century American military officer and politician.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2d08108190bab1b3325923af1d |
completed | April 17, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f3d8f188190969b75d82c6b13f0 |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:06 a.m.