Triple
T9609134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAN-nee |
E232052
|
entity |
| Predicate | stressType |
P89230
|
FINISHED |
| Object | initial stress |
—
|
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: initial stress | Statement: [FAN-nee, stressType, initial stress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stressType Context triple: [FAN-nee, stressType, initial stress]
-
A.
stressRegime
Indicates the pattern or conditions of mechanical stress applied to or experienced by an entity over time or under specific circumstances.
-
B.
strainType
Indicates the specific variety or subtype classification within a broader category of strains (e.g., biological, chemical, or product strains).
-
C.
stressed
Indicates that an entity is experiencing psychological or emotional strain or pressure, often due to challenging or demanding circumstances.
-
D.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
E.
stressesInstitution
Indicates that an entity applies pressure, demands, or strain on an institution, challenging its capacity, stability, or resources.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a8469e081909c8fb7c84ffea2b3 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:08 p.m.