Triple
T4470512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDPG |
E98481
|
entity |
| Predicate | stabilityTechnique |
P3047
|
FINISHED |
| Object | target networks |
—
|
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: target networks | Statement: [DDPG, stabilityTechnique, target networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stabilityTechnique Context triple: [DDPG, stabilityTechnique, target networks]
-
A.
stabilizedBy
Indicates that an entity’s state, structure, or behavior is made more steady, secure, or resistant to change through the influence or support of another entity.
-
B.
isStable
Indicates that the state, condition, or configuration of an entity does not change significantly over time or under expected variations in its environment.
-
C.
stabilityAxes
Indicates the axes or directions along which a system, object, or configuration remains stable or returns to equilibrium after small disturbances.
-
D.
hasStabilityLevel
Indicates that something possesses a particular degree or state of stability, often quantified or categorized along a defined scale.
-
E.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.