Triple
T19601301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard Crimson track and field teams |
E470481
|
entity |
| Predicate | conferenceRules |
P3610
|
FINISHED |
| Object | Ivy League regulations |
—
|
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: Ivy League regulations | Statement: [Harvard Crimson track and field teams, conferenceRules, Ivy League regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceRules Context triple: [Harvard Crimson track and field teams, conferenceRules, Ivy League regulations]
-
A.
communicationRule
Indicates a rule or constraint that governs how communication between entities should occur.
-
B.
governingConference
chosen
Indicates that one entity serves as the official organizing or regulatory conference overseeing another entity (such as a team, event, or institution).
-
C.
conferenceFormat
Indicates the type or structure in which a conference is organized or conducted (e.g., in-person, virtual, hybrid, workshop-based).
-
D.
adoptedRulesOfProcedureOn
Indicates that an entity formally established or approved rules of procedure on a specific date or occasion.
-
E.
conferenceStructure
Indicates how a conference is organized into its constituent parts, such as sessions, tracks, and events, and the relationships among them.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407f1fd88190aa82c4c96f755584 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.