Triple
T32308555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | first Piola–Kirchhoff stress tensor |
E825430
|
entity |
| Predicate | isGenerally |
P173954
|
FINISHED |
| Object | non-symmetric |
—
|
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: non-symmetric | Statement: [first Piola–Kirchhoff stress tensor, isGenerally, non-symmetric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGenerally Context triple: [first Piola–Kirchhoff stress tensor, isGenerally, non-symmetric]
-
A.
general
Indicates that one entity has a broad, non-specific, or overarching relationship or association with another entity.
-
B.
usedAsGeneral
Indicates that an entity served in the role or capacity of a general, typically as a high-ranking military commander.
-
C.
isGeneralPurposeIn
Indicates that something serves a broad, non-specialized function or use within a specified context, domain, or environment.
-
D.
generalRule
Indicates that something functions as a broad, overarching principle or guideline that applies across multiple specific cases or situations.
-
E.
generalCategory
Indicates that one entity is classified as a broad or overarching category to which the other entity belongs.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd89d3dc8190988bb54d492fd4a5 |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:45 a.m.