Triple
T20723557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Gray |
E509377
|
entity |
| Predicate | hasRomanticObsessionWith |
P121194
|
FINISHED |
| Object | a goat |
—
|
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: a goat | Statement: [Martin Gray, hasRomanticObsessionWith, a goat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanticObsessionWith Context triple: [Martin Gray, hasRomanticObsessionWith, a goat]
-
A.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two entities.
-
B.
romanticallyObsessedWith
chosen
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
-
C.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
D.
rumoredLoverOf
Indicates that one entity is widely believed or speculated to be the romantic partner or lover of another entity, without confirmed evidence.
-
E.
romanticRivalryWith
Indicates a mutual competitive relationship in which two entities vie for the romantic attention or affection of the same person.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e59b2081909fb6c29cb5018bb4 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:28 p.m.