Triple
T33240954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cary Scott |
E850960
|
entity |
| Predicate | loveInterestAgeRelation |
P151749
|
FINISHED |
| Object | younger man |
—
|
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: younger man | Statement: [Cary Scott, loveInterestAgeRelation, younger man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loveInterestAgeRelation Context triple: [Cary Scott, loveInterestAgeRelation, younger man]
-
A.
loveInterestType
Indicates the specific kind or category of romantic or affectionate relationship that exists between the related entities.
-
B.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
C.
loveInterest
Indicates that one entity is the romantic object of affection or attraction for another entity.
-
D.
loveInterestHasCondition
Indicates that a person’s romantic interest possesses or is affected by a particular condition or circumstance.
-
E.
ageRelation
chosen
Indicates a relationship that specifies or compares the ages of entities, such as one being older, younger, or of the same age as another.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.