Triple
T16373892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Mills |
E397631
|
entity |
| Predicate | hasDomainExpertise |
P86052
|
FINISHED |
| Object | knowledge organization |
—
|
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: knowledge organization | Statement: [Jack Mills, hasDomainExpertise, knowledge organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomainExpertise Context triple: [Jack Mills, hasDomainExpertise, knowledge organization]
-
A.
hasProfessionalDomain
chosen
Indicates that an entity operates, specializes, or is active within a particular professional field or domain.
-
B.
basedOnExpertiseOf
Indicates that something is determined, derived, or justified using the knowledge, skills, or judgment of a particular expert or group of experts.
-
C.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
D.
hasDesignExpertise
Indicates that one entity possesses specialized knowledge or skill in design related to another entity.
-
E.
hasCompetence
Indicates that an entity possesses the ability, skill, or qualification to perform a specific task or function effectively.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319d559788190bd96c45ff0900fe6 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.