Triple
T10487304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PHWA |
E247328
|
entity |
| Predicate | hasFocusLevel |
P66078
|
FINISHED |
| Object | professional level |
—
|
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 level | Statement: [PHWA, hasFocusLevel, professional level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFocusLevel Context triple: [PHWA, hasFocusLevel, professional level]
-
A.
hasFocusSystem
Indicates that one entity is the primary system or subsystem that another entity is currently directing its attention, control, or processing resources toward.
-
B.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
C.
hasFocusGroup
Indicates that an entity is associated with or participates in a specific focus group for targeted discussion, feedback, or research.
-
D.
haveFocusSystem
Indicates that an entity is currently the primary target or active focus within a system or context.
-
E.
focusLevel
chosen
Indicates the degree or intensity of attention or concentration directed toward a particular target or task.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5096a4d3481908e9c319f6cdce4f1 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.