Triple
T29162007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salim–Javed |
E739211
|
entity |
| Predicate | separatedAsDuo |
P168129
|
FINISHED |
| Object | early 1980s |
—
|
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: early 1980s | Statement: [Salim–Javed, separatedAsDuo, early 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedAsDuo Context triple: [Salim–Javed, separatedAsDuo, early 1980s]
-
A.
separatedAlongWith
Indicates that an entity becomes separated from something while simultaneously being accompanied or grouped with another specified entity during the separation.
-
B.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
C.
hasSeparatedCoupleProtagonists
Indicates that the main protagonists are a couple who are currently separated from each other, either emotionally, physically, or both.
-
D.
formedDuoWith
Indicates that two entities joined together to create a duo, typically collaborating or acting as a pair for a shared purpose or activity.
-
E.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 11:48 a.m.