Triple
T9658750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henley Rowing Club |
E233530
|
entity |
| Predicate | hasTypeOfCrew |
P21064
|
FINISHED |
| Object | sculling 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: sculling crews | Statement: [Henley Rowing Club, hasTypeOfCrew, sculling crews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfCrew Context triple: [Henley Rowing Club, hasTypeOfCrew, sculling crews]
-
A.
crewType
chosen
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
B.
hasCrewMember
Indicates that an entity includes or employs another entity as a member of its crew.
-
C.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
D.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
E.
crewComplementType
Indicates the classification or category of a crew complement associated with an entity (such as its role, composition, or staffing type).
- 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_69ca848c1ba88190b84b410cd14627fc |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bdfc3b08190835e86ff99663214 |
completed | April 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:14 p.m.