Triple
T27952236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Absolutely Immune |
E703457
|
entity |
| Predicate | originatesFromCompany |
P37135
|
FINISHED |
| Object | Act |
—
|
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: Act | Statement: [Absolutely Immune, originatesFromCompany, Act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromCompany Context triple: [Absolutely Immune, originatesFromCompany, Act]
-
A.
originatingCompany
chosen
Indicates the company from which something (such as a product, document, transaction, or request) originally comes or is issued.
-
B.
parentCompanyOfOrigin
Indicates that one company is the original parent or source company from which another company was created, derived, or spun off.
-
C.
hasMajorCompanyOrigin
Indicates that an entity originates from, was founded by, or initially developed within a major company.
-
D.
employerOrigin
Indicates that an employer entity originates from, is based in, or was founded in a specified place or source.
-
E.
includesCompaniesFrom
Indicates that a collection, group, or set contains or incorporates one or more companies as its members or elements.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 27, 2026, 7:25 p.m.