Triple
T32956441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office Bridge |
E843112
|
entity |
| Predicate | hasPortalDesign |
P1529
|
FINISHED |
| Object | rounded portal openings |
—
|
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: rounded portal openings | Statement: [Office Bridge, hasPortalDesign, rounded portal openings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortalDesign Context triple: [Office Bridge, hasPortalDesign, rounded portal openings]
-
A.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasDesigned
Indicates that one entity is the creator or designer of another entity.
-
C.
hasDesignSide
Indicates that one entity is located on, associated with, or corresponds to a particular side or face of another entity’s design.
-
D.
hasDesignStudio
Indicates that an entity owns, operates, or is associated with a design studio.
-
E.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:21 a.m.