Triple
T36870176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | schools of government |
E911203
|
entity |
| Predicate | coreActivities |
P40655
|
FINISHED |
| Object | teaching |
—
|
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: teaching | Statement: [schools of government, coreActivities, teaching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreActivities Context triple: [schools of government, coreActivities, teaching]
-
A.
businessActivities
Indicates the commercial operations, transactions, or services that an entity conducts as part of its business.
-
B.
majorActivity
chosen
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
-
C.
occupationalRootActivity
Indicates that an occupation is fundamentally based on or derived from a particular core activity or type of work.
-
D.
earnActivity
Indicates that an entity gains or receives something of value (such as money, points, or rewards) as a result of performing a particular activity.
-
E.
activitiesCarriedOutFor
Indicates that certain activities are performed on behalf of, in service of, or for the benefit of a particular 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.