Triple
T16148712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | higher education association council |
E391854
|
entity |
| Predicate | mayIncludeMembers |
P1598
|
FINISHED |
| Object | public universities |
—
|
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: public universities | Statement: [higher education association council, mayIncludeMembers, public universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeMembers Context triple: [higher education association council, mayIncludeMembers, public universities]
-
A.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
B.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
C.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
D.
additionalMembersAllowed
chosen
Indicates that more members are permitted to be added beyond those already included or initially specified.
-
E.
membershipConsistsOf
Indicates that a membership is composed of, or includes, specific member entities as its constituents.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9551e081908391061b092ff31b |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.