Triple
T23738756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cal Weaver |
E586607
|
entity |
| Predicate | receivesDatingAdviceFrom |
P153501
|
FINISHED |
| Object | Jacob Palmer |
—
|
NE NERFINISHED |
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: Jacob Palmer | Statement: [Cal Weaver, receivesDatingAdviceFrom, Jacob Palmer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesDatingAdviceFrom Context triple: [Cal Weaver, receivesDatingAdviceFrom, Jacob Palmer]
-
A.
usedForDating
Indicates a relationship where one entity is used as a means, tool, or context for engaging in romantic or dating activities with another entity.
-
B.
scientificDating
Indicates that an object or material has been assigned an age or time period using scientific dating methods (e.g., radiocarbon, dendrochronology, or other analytical techniques).
-
C.
asksToMarry
Indicates that one entity proposes marriage to another, requesting that they become spouses.
-
D.
roleInTinder
Indicates the specific function or position an entity holds within the context of the Tinder platform or interaction.
-
E.
likelyDatingTo
Indicates that something probably originates from or was created in a particular time period or date range.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad427f081908eaf96273fec757b |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:11 p.m.