Triple
T4929988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIBA Part 1 |
E110669
|
entity |
| Predicate | typicalProgression |
P12146
|
FINISHED |
| Object | year-out in architectural practice |
—
|
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: year-out in architectural practice | Statement: [RIBA Part 1, typicalProgression, year-out in architectural practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProgression Context triple: [RIBA Part 1, typicalProgression, year-out in architectural practice]
-
A.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
typicalConsistency
Indicates that one entity characteristically maintains a regular or expected level of consistency in relation to another entity or context.
-
D.
typicalPractice
chosen
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
E.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd703a0fa48190809b6ac3f2731349 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.