Triple
T172740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durham boat |
E3510
|
entity |
| Predicate | hasTypicalCrewSize |
P883
|
FINISHED |
| Object | 2 to 4 |
—
|
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: 2 to 4 | Statement: [Durham boat, hasTypicalCrewSize, 2 to 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalCrewSize Context triple: [Durham boat, hasTypicalCrewSize, 2 to 4]
-
A.
crewCountApproximate
chosen
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
B.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
C.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
-
D.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
E.
passengersCountApproximate
Indicates that the number of passengers involved is given as an approximate or estimated count rather than an exact figure.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a256689f908190afeb5ee82022a911 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.