Triple
T7216216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Progressive Architecture Award |
E149541
|
entity |
| Predicate | typicalStatusOfProjects |
P39444
|
FINISHED |
| Object | unbuilt |
—
|
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: unbuilt | Statement: [Progressive Architecture Award, typicalStatusOfProjects, unbuilt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStatusOfProjects Context triple: [Progressive Architecture Award, typicalStatusOfProjects, unbuilt]
-
A.
typicalProjectTypes
Indicates the kinds or categories of projects that are most commonly or characteristically associated with a given entity.
-
B.
statusOfOriginalProject
Indicates the current state or condition of the original project in relation to its lifecycle or progress.
-
C.
typicalBusinessStatus
Indicates the usual or standard operational status or condition of a business (e.g., active, inactive, seasonal) under normal circumstances.
-
D.
worksStatus
chosen
Indicates the current state or condition of an entity’s work or project, such as whether it is planned, in progress, completed, or otherwise categorized.
-
E.
projectOutcome
Indicates the resulting state, impact, or consequences produced by carrying out a project.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e99000dc81908ef4b70729cc00b0 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:53 p.m.