Triple
T31178170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Power |
E794810
|
entity |
| Predicate | hasPossibleOccupation |
P154940
|
FINISHED |
| Object | professional |
—
|
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: professional | Statement: [Brian Power, hasPossibleOccupation, professional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPossibleOccupation Context triple: [Brian Power, hasPossibleOccupation, professional]
-
A.
hasOccupationInferred
Indicates that an entity is inferred, rather than explicitly stated, to have a particular occupation or professional role.
-
B.
hasOccupationAttribute
Indicates that an entity possesses a specific characteristic, quality, or attribute related to its occupation or job.
-
C.
hasOccupationInWork
Indicates that an entity holds or performs a specific occupation within a particular work, project, or creative production.
-
D.
hasOccupationCombination
Indicates that an entity holds multiple occupations or job roles in combination.
-
E.
mayBeOccupationOf
chosen
Indicates that something is a possible or potential occupation held by a given entity.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 29, 2026, 9:08 p.m.