Triple
T5632474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rénergie |
E147865
|
entity |
| Predicate | targetConcern |
P64698
|
FINISHED |
| Object | loss of firmness |
—
|
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: loss of firmness | Statement: [Rénergie, targetConcern, loss of firmness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetConcern Context triple: [Rénergie, targetConcern, loss of firmness]
-
A.
concern
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
B.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
strategicConcernFor
Indicates a relationship where one entity considers another entity’s situation, actions, or outcomes important for its own long-term goals, risks, or strategic interests.
-
D.
commandConcerning
Indicates that one entity issues an order or directive specifically about another entity or subject.
-
E.
concernsLayer
Indicates that something is related or pertains specifically to a particular layer within a layered structure or system.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225e8e848190a9ccd48fc0d74e5c |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:40 p.m.