Triple
T6784291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulcrum |
E155760
|
entity |
| Predicate | appliesToDesignFeature |
P17265
|
FINISHED |
| Object | leading-edge root extensions |
—
|
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: leading-edge root extensions | Statement: [Fulcrum, appliesToDesignFeature, leading-edge root extensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToDesignFeature Context triple: [Fulcrum, appliesToDesignFeature, leading-edge root extensions]
-
A.
appliesToFeature
chosen
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
B.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
D.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
E.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d28bdc3c8190aa60616d89db66ed |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.