Triple
T36367905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAP (Multidisciplinary Action Projects) |
E895675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | consulting project course |
C66308
|
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: consulting project course Context triple: [MAP (Multidisciplinary Action Projects), instanceOf, consulting project course]
-
A.
architectural consulting project
An architectural consulting project is a professional engagement in which architects analyze client needs, evaluate existing conditions, and develop strategic design recommendations, plans, and guidance to inform and optimize building or spatial development decisions.
-
B.
public survey project
A public survey project is an organized effort to collect, analyze, and report data on opinions, behaviors, or characteristics from a defined population using systematically designed questionnaires or interviews.
-
C.
public works project
A public works project is a government-funded initiative to plan, construct, or maintain infrastructure and facilities that serve the general public’s needs and welfare.
-
D.
project-based curriculum
chosen
A project-based curriculum is an educational approach in which students learn key concepts and skills by actively engaging in extended, real-world projects that require inquiry, collaboration, and problem-solving.
-
E.
studio project
A studio project is a creative, often collaborative, hands-on assignment in a studio-based course where students design, develop, and present work that applies theoretical concepts to practical, real-world or experimental problems.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.