Triple
T37782528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay 12 Games |
E941867
|
entity |
| Predicate | companyScale |
P145324
|
FINISHED |
| Object | small studio |
—
|
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: small studio | Statement: [Bay 12 Games, companyScale, small studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyScale Context triple: [Bay 12 Games, companyScale, small studio]
-
A.
typicalCompanySize
Indicates the usual or most common number of employees associated with a company.
-
B.
associatedWithCompanySize
chosen
Indicates that an entity has a relationship to, or is characterized or categorized by, the size of a company (e.g., small, medium, large).
-
C.
businessScale
Indicates the relative size or level of operations of a business, such as its scope, capacity, or market reach.
-
D.
appliesToEmployerSize
Indicates that something (such as a rule, policy, or condition) is applicable only to employers of a specified size or within a defined employer size range.
-
E.
staffSize
Indicates the number of staff members associated with an 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.