Triple
T10726612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amar Doman |
E252962
|
entity |
| Predicate | businessRoleAtFuturaCorporation |
P44925
|
FINISHED |
| Object | founder |
—
|
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: founder | Statement: [Amar Doman, businessRoleAtFuturaCorporation, founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessRoleAtFuturaCorporation Context triple: [Amar Doman, businessRoleAtFuturaCorporation, founder]
-
A.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
B.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
C.
roleInFinance
Indicates that an entity holds a specific function, responsibility, or position within a financial context, system, or transaction.
-
D.
employedRole
chosen
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
E.
roleWithinRaytheon
Indicates that one entity holds or has held a specific role, position, or function within the organization Raytheon.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70fc713f081909ba1d1b986c1fe5c |
completed | April 9, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.