Triple
T28337633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caproni Ca.60 Noviplano |
E717720
|
entity |
| Predicate | intendedPassengerCapacity |
P11680
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [Caproni Ca.60 Noviplano, intendedPassengerCapacity, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPassengerCapacity Context triple: [Caproni Ca.60 Noviplano, intendedPassengerCapacity, 100]
-
A.
maximumPassengerCapacity
chosen
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
B.
passengerCapacityCategory
Indicates the classification of an entity based on the number of passengers it is designed or allowed to carry.
-
C.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
D.
hasPassengerArea
Indicates that an object or vehicle includes a designated area intended for carrying passengers.
-
E.
crewAndPassengersCount
Indicates the total number of people on a vehicle or vessel, combining both crew members and passengers.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 12:37 a.m.