Triple
T11844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augmentation Research Center |
E241
|
entity |
| Predicate | developedFor |
P98
|
FINISHED |
| Object | interactive knowledge work |
—
|
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: interactive knowledge work | Statement: [Augmentation Research Center, developedFor, interactive knowledge work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedFor Context triple: [Augmentation Research Center, developedFor, interactive knowledge work]
-
A.
developedAt
Indicates the place or location where something was created, built, or developed.
-
B.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
C.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a241ea1ea081908e8a81ca97531ba5 |
completed | Feb. 28, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69a23fe7da8c8190aea795b62cb91621 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.