Triple
T12761368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPK21 |
E305001
|
entity |
| Predicate | hasWorkspaceType |
P32186
|
FINISHED |
| Object | open-plan |
—
|
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: open-plan | Statement: [MPK21, hasWorkspaceType, open-plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkspaceType Context triple: [MPK21, hasWorkspaceType, open-plan]
-
A.
hasSpaceType
chosen
Indicates that one entity is associated with, or classified by, a particular type or category of space.
-
B.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
C.
hasWorkTypeRelation
Indicates a relationship specifying the type or category of work associated with an entity.
-
D.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
-
E.
hasApplicationType
Indicates that an entity is associated with or classified by a specific type or category of 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8e44188190840cd23d380bf23d |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.