Triple
T32673862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Load-Out |
E835372
|
entity |
| Predicate | famouslyPairedWith |
P119636
|
FINISHED |
| Object | Stay |
—
|
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: Stay | Statement: [The Load-Out, famouslyPairedWith, Stay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famouslyPairedWith Context triple: [The Load-Out, famouslyPairedWith, Stay]
-
A.
famousTogetherWith
chosen
Indicates that two entities share fame or public recognition in association with each other, such that their notability is linked or commonly referenced together.
-
B.
isFianceeOf
Indicates that one person is the engaged-to-be-married partner of another person.
-
C.
marriedToBeforeFameOf
Indicates that one person was married to another person before the latter became famous.
-
D.
accompaniesTo
Indicates that one entity goes along with or escorts another entity to a specific destination or event.
-
E.
notableCouple
Indicates that two entities are widely recognized or documented as a couple in a notable or significant relationship.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:09 a.m.