Triple
T29416962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BioWare Austin |
E746050
|
entity |
| Predicate | settingOfOffice |
P17674
|
FINISHED |
| Object | corporate office building in Austin |
—
|
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: corporate office building in Austin | Statement: [BioWare Austin, settingOfOffice, corporate office building in Austin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfOffice Context triple: [BioWare Austin, settingOfOffice, corporate office building in Austin]
-
A.
typeOfOffice
Indicates the specific category or kind of office that an office entity belongs to (e.g., executive, legislative, judicial, or other office types).
-
B.
natureOfOffice
Indicates the type or character of an office or position, specifying what kind of role or function it represents.
-
C.
servesAsOfficeOf
chosen
Indicates that one entity functions as the official office, headquarters, or administrative base for another entity.
-
D.
aimOfOffice
Indicates that a particular goal, purpose, or objective is the intended aim of a given office or official position.
-
E.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 3:02 p.m.