Triple
T23470471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale junior varsity teams |
E569212
|
entity |
| Predicate | typicalRosterComposition |
P10366
|
FINISHED |
| Object | underclassmen |
—
|
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: underclassmen | Statement: [Yale junior varsity teams, typicalRosterComposition, underclassmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRosterComposition Context triple: [Yale junior varsity teams, typicalRosterComposition, underclassmen]
-
A.
typicalTeamComposition
chosen
Indicates the usual or standard combination of roles or members that make up a team.
-
B.
typicalRosterSource
Indicates that one entity is the usual or standard source from which the other entity’s roster or list of members is derived.
-
C.
typicalFormation
Indicates the usual or characteristic way in which something is formed, structured, or comes into existence.
-
D.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
-
E.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6ff8dc0819086961b1f07030d9c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.