Triple
T7936051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EISA |
E184290
|
entity |
| Predicate | mechanicalDesign |
P79885
|
FINISHED |
| Object | two-level slot to accept ISA and EISA cards |
—
|
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: two-level slot to accept ISA and EISA cards | Statement: [EISA, mechanicalDesign, two-level slot to accept ISA and EISA cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicalDesign Context triple: [EISA, mechanicalDesign, two-level slot to accept ISA and EISA cards]
-
A.
mechanicalDesigner
Indicates that one entity is responsible for designing or engineering mechanical components, systems, or devices for another entity or project.
-
B.
designModel
Indicates that one entity creates, specifies, or defines the structure or behavior of another entity as a model or blueprint.
-
C.
mechanicalCompatibility
Indicates that two entities can function together properly from a mechanical standpoint, without interference, damage, or performance issues.
-
D.
mechanicalProperty
Indicates a relationship where a mechanical characteristic (such as strength, stiffness, hardness, or elasticity) is attributed to or associated with an entity.
-
E.
designDiscipline
Indicates a relationship where an entity is associated with, categorized under, or practices a particular field or branch of design.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aede3cc81908b0d3b54e68997b9 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:08 p.m.