Triple
T1041639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Automattic |
E22480
|
entity |
| Predicate | workModel |
P23848
|
FINISHED |
| Object | fully remote company |
—
|
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: fully remote company | Statement: [Automattic, workModel, fully remote company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workModel Context triple: [Automattic, workModel, fully remote company]
-
A.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
B.
workScope
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
-
C.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of another entity.
-
D.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
E.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b845fa8c8190a7b69629883b62e2 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8444f708190815732408aa0463e |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.