Triple
T30801885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Descent: Freespace – The Great War (Amiga port) |
E784389
|
entity |
| Predicate | hasPlayableVehicleType |
P185321
|
FINISHED |
| Object | space fighter |
—
|
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: space fighter | Statement: [Descent: Freespace – The Great War (Amiga port), hasPlayableVehicleType, space fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayableVehicleType Context triple: [Descent: Freespace – The Great War (Amiga port), hasPlayableVehicleType, space fighter]
-
A.
vehicleEligibility
Indicates whether a given vehicle satisfies the required conditions or criteria to be considered eligible for a specified purpose or program.
-
B.
hasVehicle
Indicates that one entity possesses, owns, or is assigned a vehicle.
-
C.
appliedToVehicleType
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
-
D.
hasVehicularUse
Indicates that something is used for, intended for, or associated with operation by vehicles or vehicular traffic.
-
E.
canDrive
Indicates that one entity has the ability or permission to operate a vehicle or drive another entity.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: April 29, 2026, 8:42 p.m.