Triple
T31496706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zenit reconnaissance satellites |
E803560
|
entity |
| Predicate | hadCrewCapacity |
P8587
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Zenit reconnaissance satellites, hadCrewCapacity, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCrewCapacity Context triple: [Zenit reconnaissance satellites, hadCrewCapacity, 0]
-
A.
hasCrewCapacity
chosen
Indicates that an entity is capable of accommodating a specified number of crew members.
-
B.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
C.
crewAndPassengersCount
Indicates the total number of people on a vehicle or vessel, combining both crew members and passengers.
-
D.
maximumPassengerCapacity
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
E.
carriesCrewOf
Indicates that one entity serves as the vehicle or vessel that transports the crew belonging to another entity.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1ea029c8190ab83ffdf6a18caf8 |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:41 p.m.