Triple
T9094359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jon Gluyas |
E217976
|
entity |
| Predicate | expertise |
P18508
|
FINISHED |
| Object | petroleum systems |
—
|
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: petroleum systems | Statement: [Jon Gluyas, expertise, petroleum systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expertise Context triple: [Jon Gluyas, expertise, petroleum systems]
-
A.
competence
Indicates that an entity has the ability, skill, or qualification to perform a task or fulfill a role effectively.
-
B.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
C.
experienceIncludes
Indicates that a particular experience encompasses, contains, or involves a specified component, activity, or element as part of it.
-
D.
hasDesignExpertise
Indicates that one entity possesses specialized knowledge or skill in design related to another entity.
-
E.
competenceArea
chosen
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b4a2e0819092f4eae8b1d21f33 |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:14 p.m.