Triple
T29416965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BioWare Austin |
E746050
|
entity |
| Predicate | hasNotableIP |
P200881
|
FINISHED |
| Object | Star Wars: The Old Republic live service |
—
|
NE NERFINISHED |
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: Star Wars: The Old Republic live service | Statement: [BioWare Austin, hasNotableIP, Star Wars: The Old Republic live service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableIP Context triple: [BioWare Austin, hasNotableIP, Star Wars: The Old Republic live service]
-
A.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
-
B.
hasIP
Indicates that one entity possesses, is assigned, or is associated with a specific IP address.
-
C.
hasNotableNetwork
Indicates that one entity is recognized for having a significant, influential, or widely connected network or set of relationships with other entities.
-
D.
hasNotableIdentity
Indicates that an entity is recognized for a specific, distinguished role, status, or identity that makes it notable.
-
E.
hasNotableNumber
Indicates that an entity is associated with a specific number that is considered significant, distinctive, or noteworthy in some context.
- F. None of above. chosen
Provenance (4 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_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
| PDg | Predicate description generation | batch_69ffb6976f84819098a9b14946591baa |
completed | May 9, 2026, 10:35 p.m. |
Created at: April 28, 2026, 3:02 p.m.