Triple
T29836738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nehru Trophy Boat Race |
E757675
|
entity |
| Predicate | numberOfRowersPerBoat |
P198545
|
FINISHED |
| Object | approximately 100 |
—
|
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: approximately 100 | Statement: [Nehru Trophy Boat Race, numberOfRowersPerBoat, approximately 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRowersPerBoat Context triple: [Nehru Trophy Boat Race, numberOfRowersPerBoat, approximately 100]
-
A.
numberOfRowers
chosen
Indicates the quantity of rowers associated with or required for a given boat, event, or rowing context.
-
B.
oarsPerRower
Indicates the number of oars assigned to or used by each individual rower in a rowing context.
-
C.
numberOfBoatsWidth
Indicates the count of boats arranged or present across the width of a given area or span.
-
D.
typeOfRowing
Indicates the specific style or category of rowing associated with an entity (e.g., sweep rowing, sculling, indoor rowing).
-
E.
isRowingCompanionOf
Indicates that one entity accompanies another in the activity of rowing, typically sharing a boat or rowing effort together.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: April 29, 2026, 5:37 p.m.