Triple
T31136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division I Men’s Basketball Tournament |
E621
|
entity |
| Predicate | originalNumberOfTeams |
P1131
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [NCAA Division I Men’s Basketball Tournament, originalNumberOfTeams, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNumberOfTeams Context triple: [NCAA Division I Men’s Basketball Tournament, originalNumberOfTeams, 8]
-
A.
numberOfParticipants
chosen
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
B.
originalBAATeam
Indicates that an entity is (or was) a member of the original BAA team associated with another entity (such as an organization, project, or initiative).
-
C.
numberOfPositions
Indicates the total count of distinct positions or roles associated with a given entity.
-
D.
originalLeague
Indicates the league or competition in which an entity (such as a team or club) initially participated or was first a member.
-
E.
originalSixMember
Indicates that an entity was one of the six original members of a specific group, organization, or set.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a249ec0d288190ac3a0939db61813b |
completed | Feb. 28, 2026, 1:50 a.m. |
| PD | Predicate disambiguation | batch_69a24870417081909c7c01e400c94716 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.