Triple
T5792451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA conferences |
E128425
|
entity |
| Predicate | typicalMemberCount |
P8561
|
FINISHED |
| Object | between 8 and 16 full members |
—
|
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: between 8 and 16 full members | Statement: [NCAA conferences, typicalMemberCount, between 8 and 16 full members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMemberCount Context triple: [NCAA conferences, typicalMemberCount, between 8 and 16 full members]
-
A.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
B.
typicalGroupSizeRange
chosen
Indicates the usual minimum and maximum number of individuals that typically occur together in a group for the given entity.
-
C.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
-
D.
minimumNumberOfMembers
Indicates the smallest allowable or required number of members that must be present or involved in a given context or group.
-
E.
limitedNumberOfMembers
Indicates that the associated group or entity has a maximum allowed number of members or participants.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a5870b88190bbfaac2782635128 |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.