Triple
T27993459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia High School Association |
E706941
|
entity |
| Predicate | activityTypeGoverned |
P105347
|
FINISHED |
| Object | boys athletics |
—
|
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: boys athletics | Statement: [Georgia High School Association, activityTypeGoverned, boys athletics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityTypeGoverned Context triple: [Georgia High School Association, activityTypeGoverned, boys athletics]
-
A.
activityControlled
Indicates that one entity regulates, directs, or manages the activity or behavior of another entity.
-
B.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
C.
mannerOfActivity
Indicates the way or style in which an activity is performed or carried out.
-
D.
permittedActivity
Indicates that a particular action or behavior is allowed or authorized within a given context or under specified rules.
-
E.
governedCategory
chosen
Indicates that one category is subject to the control, regulation, or authority of another entity or governing framework.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 7:51 p.m.