Triple
T32956494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office Bridge |
E843114
|
entity |
| Predicate | hasPortalType |
P130953
|
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, hasPortalType, rounded portal openings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortalType Context triple: [Office Bridge, hasPortalType, rounded portal openings]
-
A.
hasPortal
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
-
B.
portalType
chosen
Indicates the kind or category of portal through which an entity is accessed or presented.
-
C.
hasPortalNamespace
Indicates that an entity is associated with or belongs to a specific portal namespace within a system.
-
D.
hasPortType
Indicates that an entity is associated with, or characterized by, a specific type or category of port.
-
E.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
- 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_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 1:21 a.m.