Triple
T25177272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yonah |
E630481
|
entity |
| Predicate | targetFormFactor |
P161443
|
FINISHED |
| Object | notebooks |
—
|
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: notebooks | Statement: [Yonah, targetFormFactor, notebooks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetFormFactor Context triple: [Yonah, targetFormFactor, notebooks]
-
A.
hasFormFactor
Indicates that one entity possesses or is characterized by a particular physical or structural form factor defined by another entity.
-
B.
deviceShape
Indicates that one entity has the physical form or geometric configuration specified by the other entity.
-
C.
supportsDriveFormFactor
Indicates that one entity is compatible with or can accommodate a specified physical form factor of a drive.
-
D.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
E.
supportsFormFactorFamily
Indicates that one entity is compatible with and can operate using a specified family of physical or design form factors.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 21, 2026, 12:34 p.m.