Triple
T251255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reedy Creek Improvement District |
E5150
|
entity |
| Predicate | createdForProject |
P7551
|
FINISHED |
| Object | development of Walt Disney World |
—
|
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: development of Walt Disney World | Statement: [Reedy Creek Improvement District, createdForProject, development of Walt Disney World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdForProject Context triple: [Reedy Creek Improvement District, createdForProject, development of Walt Disney World]
-
A.
createdFor
chosen
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by another entity.
-
B.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
-
C.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
-
D.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
-
E.
createdProgram
Indicates that an entity authored, developed, or produced a particular program (such as software or a coded application).
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.