Triple
T8128868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Grace Challenge Cup |
E189804
|
entity |
| Predicate | oarsPerRower |
P81628
|
FINISHED |
| Object | two |
—
|
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: two | Statement: [Princess Grace Challenge Cup, oarsPerRower, two]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oarsPerRower Context triple: [Princess Grace Challenge Cup, oarsPerRower, two]
-
A.
estimatedOarCount
Indicates the estimated number of oars associated with an entity, typically approximating how many oars it has or uses.
-
B.
hasOarHoles
Indicates that an object possesses holes specifically designed to hold or accommodate oars.
-
C.
rowedFor
Indicates that one entity served as a rower or member of the rowing team representing another entity, such as an institution, club, or country.
-
D.
ridersPerRow
Indicates the number of riders assigned or allowed to sit in each row.
-
E.
crewCount
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
- F. None of above. chosen
Provenance (4 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4c496a8c81909aea840248d85d50 |
completed | March 31, 2026, 4:23 a.m. |
Created at: March 30, 2026, 5:34 p.m.