Triple
T38051234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Connelly |
E949763
|
entity |
| Predicate | romanticMeetingPlace |
P50741
|
FINISHED |
| Object | rooftop party in New York |
—
|
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: rooftop party in New York | Statement: [Louis Connelly, romanticMeetingPlace, rooftop party in New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticMeetingPlace Context triple: [Louis Connelly, romanticMeetingPlace, rooftop party in New York]
-
A.
romanticArcLocation
Indicates the place or setting where a romantic storyline or relationship development occurs.
-
B.
romanticSceneWith
Indicates a scene or situation in which the two entities are engaged together in a romantic context or interaction.
-
C.
rendezvousWith
Indicates that two or more entities meet or come together at an agreed place and time, often for a specific purpose.
-
D.
romanticPlotFunction
Indicates a narrative relationship where characters are involved in or contribute to a romantic storyline or romantic development within the plot.
-
E.
meetingPlaceOf
chosen
Indicates the location where a particular meeting or gathering takes place or is held for the referenced entities.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.