Triple
T31703212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin |
E809112
|
entity |
| Predicate | heightens |
P7907
|
FINISHED |
| Object | tension between May and Eddie |
—
|
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: tension between May and Eddie | Statement: [Martin, heightens, tension between May and Eddie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightens Context triple: [Martin, heightens, tension between May and Eddie]
-
A.
increases
chosen
Indicates that one entity causes another entity’s value, level, or intensity to become larger or higher.
-
B.
strengthens
Indicates that one entity increases the power, effectiveness, or resilience of another.
-
C.
exaggerates
Indicates that one entity portrays something about another entity or situation as greater, more extreme, or more significant than it actually is.
-
D.
strengthensFrom
Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
-
E.
intensifiedOver
Indicates that one entity increases the degree, strength, or intensity of another entity or condition beyond its previous level.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:12 p.m.