Triple
T35842905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Fravor |
E1036133
|
entity |
| Predicate | describedObjectPropulsionAs |
P193966
|
FINISHED |
| Object | no visible means of propulsion |
—
|
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: no visible means of propulsion | Statement: [David Fravor, describedObjectPropulsionAs, no visible means of propulsion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedObjectPropulsionAs Context triple: [David Fravor, describedObjectPropulsionAs, no visible means of propulsion]
-
A.
selfPropelled
Indicates that an entity moves or operates by its own internal power or mechanism, without needing an external force to propel it.
-
B.
originalPropulsion
Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
-
C.
propulsionTypeMeaning
Indicates the specific kind of propulsion system or mechanism by which something is powered or driven.
-
D.
propulsionMedium
Indicates the medium or substance through which propulsion is generated or transmitted for movement.
-
E.
plannedPropulsionType
Indicates the type of propulsion system that is intended or scheduled to be used for an object or vehicle.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: May 3, 2026, 4:06 p.m.