Triple
T10478604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Rowing Race |
E247109
|
entity |
| Predicate | typicalCrewSizeRange |
P30694
|
FINISHED |
| Object | 1 to 8 rowers |
—
|
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: 1 to 8 rowers | Statement: [Atlantic Rowing Race, typicalCrewSizeRange, 1 to 8 rowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCrewSizeRange Context triple: [Atlantic Rowing Race, typicalCrewSizeRange, 1 to 8 rowers]
-
A.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
B.
crewCount
chosen
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
C.
typicalGroupSizeRange
Indicates the usual minimum and maximum number of individuals that typically occur together in a group for the given entity.
-
D.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
E.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095a25708190bf34e3ca1491e003 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:21 p.m.