Triple
T29768734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Strategic Campaign Plan |
E753988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint planning product |
C11101
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: joint planning product Context triple: [Joint Strategic Campaign Plan, instanceOf, joint planning product]
-
A.
planned sector
A planned sector is a designated area within a city or region that is systematically organized and developed according to a comprehensive plan for land use, infrastructure, and services.
-
B.
plan
chosen
A plan is a structured set of intended actions and decisions, organized over time and resources, to achieve specific goals or outcomes.
-
C.
planning library
A planning library is a reusable collection of algorithms, data structures, and tools that support the creation, evaluation, and optimization of plans or schedules within software applications.
-
D.
tribute product
A tribute product is a specially designed item created to honor, commemorate, or celebrate a person, event, brand, or cultural phenomenon, often by incorporating recognizable themes, symbols, or stylistic elements associated with the original subject.
-
E.
planned development
A planned development is a real estate project in which land use, building placement, density, and amenities are comprehensively designed and approved as a unified, coordinated plan rather than as individual, piecemeal developments.
- F. None of above.
Provenance (1 batch)
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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 8:40 p.m.