Triple
T22982538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arista AB 4199 |
E571508
|
entity |
| Predicate | matrixNumberType |
P130788
|
FINISHED |
| Object | runout groove identifier |
—
|
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: runout groove identifier | Statement: [Arista AB 4199, matrixNumberType, runout groove identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matrixNumberType Context triple: [Arista AB 4199, matrixNumberType, runout groove identifier]
-
A.
numericType
Indicates that one entity specifies or constrains the kind or category of numeric value associated with another entity.
-
B.
hasMatrixType
Indicates that an entity is associated with or characterized by a specific type or category of matrix.
-
C.
magmaType
Indicates the specific classification or type of magma associated with or characterizing an entity.
-
D.
hasMatrixNumber
chosen
Indicates that an entity is associated with a specific matrix identification number used to uniquely reference it.
-
E.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829645f88190aea1b96ea595ff60 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.