Triple
T7820217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge University Cricket Club |
E181109
|
entity |
| Predicate | firstClassStatus |
P50616
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cambridge University Cricket Club, firstClassStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstClassStatus Context triple: [Cambridge University Cricket Club, firstClassStatus, true]
-
A.
firstPartyStatus
Indicates that an entity holds the role or position of the primary or original party in a given relationship, agreement, or interaction.
-
B.
seatClass
chosen
Indicates the travel or seating category assigned to a passenger or seat (e.g., economy, business, first class).
-
C.
eliteStatusProgram
Indicates a relationship where an entity is enrolled in or associated with a special high-tier or privileged status program.
-
D.
firstTier
Indicates that one entity occupies the highest or primary level, rank, or priority relative to others in a hierarchical structure.
-
E.
hasPrioritySeating
Indicates that one entity provides or designates reserved or preferential seating for another entity.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa06d28881908d62d4c02b45cedd |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:41 p.m.