Triple
T26910505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head of the River Race |
E677369
|
entity |
| Predicate | typicalEntryLimit |
P69034
|
FINISHED |
| Object | over 400 crews |
—
|
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: over 400 crews | Statement: [Head of the River Race, typicalEntryLimit, over 400 crews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntryLimit Context triple: [Head of the River Race, typicalEntryLimit, over 400 crews]
-
A.
typicalEntryList
Indicates a relationship where an entity is associated with a standard or representative list of entries that are commonly or normally linked to it.
-
B.
maximumEntries
chosen
Indicates the relationship that specifies the highest number of entries that are allowed or supported in a given context.
-
C.
typicalEntryType
Indicates the usual or standard category or kind of entry associated with something.
-
D.
numberOfEntries
Indicates the total count of individual items, records, or instances associated with a given entity or context.
-
E.
visitorLimit
Indicates a constraint specifying the maximum number of visitors allowed for a given entity or context.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 27, 2026, 6:01 a.m.