Triple
T29683686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivienne Marcheline Jolie-Pitt |
E751024
|
entity |
| Predicate | hasPubliclyKnownLastName |
P138229
|
FINISHED |
| Object | Jolie-Pitt |
—
|
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: Jolie-Pitt | Statement: [Vivienne Marcheline Jolie-Pitt, hasPubliclyKnownLastName, Jolie-Pitt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPubliclyKnownLastName Context triple: [Vivienne Marcheline Jolie-Pitt, hasPubliclyKnownLastName, Jolie-Pitt]
-
A.
hasNotableSurname
chosen
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
-
B.
fullNameRevealed
Indicates that an entity’s complete personal name has been disclosed or made known to another party or in a given context.
-
C.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
D.
hasGivenNames
Indicates that an entity possesses one or more personal (given) names assigned to it.
-
E.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 7:12 p.m.