Triple
T21886558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signum |
E540419
|
entity |
| Predicate | lineSideEquipment |
P113532
|
FINISHED |
| Object | permanent magnets |
—
|
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: permanent magnets | Statement: [Signum, lineSideEquipment, permanent magnets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineSideEquipment Context triple: [Signum, lineSideEquipment, permanent magnets]
-
A.
hasAuxiliaryEquipment
Indicates that one entity is equipped with, or accompanied by, additional supporting equipment associated with another entity.
-
B.
operatesOnSide
Indicates that an action or process is performed specifically on a particular side or lateral aspect of an object or entity.
-
C.
equipmentIncludes
chosen
Indicates that one entity contains, comprises, or has as part of its set of items a specified piece or set of equipment.
-
D.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
E.
notableGroundEquipment
Indicates that there is ground-based equipment at or associated with an entity that is considered significant or noteworthy in some context.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.