Triple
T177262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-Eastern Athletic Conference |
E3599
|
entity |
| Predicate | membershipCategory |
P4027
|
FINISHED |
| Object | HBCU conference |
—
|
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: HBCU conference | Statement: [Mid-Eastern Athletic Conference, membershipCategory, HBCU conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipCategory Context triple: [Mid-Eastern Athletic Conference, membershipCategory, HBCU conference]
-
A.
memberCategory
chosen
Indicates that an entity belongs to or is classified under a specific category or group.
-
B.
membershipPeak
Indicates the time or period at which an entity’s membership in a group or organization reaches its highest level.
-
C.
membershipSpread
Indicates how widely membership in a group, organization, or category is distributed across different entities or locations.
-
D.
memberTitle
Indicates the formal title or designation held by a member within a group, organization, or body.
-
E.
memberOf
Indicates that an entity belongs to, is part of, or is a constituent of a larger group, organization, or collection.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258fd278481908ad4498e03f38e2f |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.