Triple
T250773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSV Limiting Factor |
E5141
|
entity |
| Predicate | hasCrewCapacity |
P8587
|
FINISHED |
| Object | 3 people |
—
|
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: 3 people | Statement: [DSV Limiting Factor, hasCrewCapacity, 3 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewCapacity Context triple: [DSV Limiting Factor, hasCrewCapacity, 3 people]
-
A.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
B.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
C.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
D.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
E.
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).
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.