Triple
T24976700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Twenty |
E625040
|
entity |
| Predicate | foldingMechanismLocation |
P157494
|
FINISHED |
| Object | main frame hinge |
—
|
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: main frame hinge | Statement: [Raleigh Twenty, foldingMechanismLocation, main frame hinge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foldingMechanismLocation Context triple: [Raleigh Twenty, foldingMechanismLocation, main frame hinge]
-
A.
hasSlidingMechanism
Indicates that one entity possesses or incorporates a mechanism that allows parts of it to move smoothly along a track or surface in a sliding motion.
-
B.
tiltingMechanism
Indicates a relationship where one entity serves as a mechanism that enables another entity to tilt or be tilted.
-
C.
folding
chosen
Indicates that one entity bends or doubles another entity (or itself) so that parts of it lie flat against or over each other.
-
D.
foldingType
Indicates the specific manner or configuration in which something is folded or arranged into a folded form.
-
E.
wingFolding
Indicates that an entity folds or can fold its wings, typically transitioning them from an extended to a closed or resting position.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:02 a.m.