Triple
T30933744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Resources |
E788062
|
entity |
| Predicate | hasSubfunction |
P130600
|
FINISHED |
| Object | recruitment and staffing |
—
|
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: recruitment and staffing | Statement: [Human Resources, hasSubfunction, recruitment and staffing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubfunction Context triple: [Human Resources, hasSubfunction, recruitment and staffing]
-
A.
hasSubordinateFunction
chosen
Indicates that one function operates under the authority, control, or scope of another function as its subordinate.
-
B.
hasSubService
Indicates that one service includes or is composed of another, more specific service as a subordinate or component part.
-
C.
containsFunction
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
D.
hasUpperLevelFunction
Indicates that one function operates at a higher or more abstract level than another function within a hierarchical relationship.
-
E.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 29, 2026, 8:52 p.m.