Triple
T29683685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivienne Marcheline Jolie-Pitt |
E751024
|
entity |
| Predicate | hasPubliclyKnownFirstName |
P172753
|
FINISHED |
| Object | Vivienne |
—
|
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: Vivienne | Statement: [Vivienne Marcheline Jolie-Pitt, hasPubliclyKnownFirstName, Vivienne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPubliclyKnownFirstName Context triple: [Vivienne Marcheline Jolie-Pitt, hasPubliclyKnownFirstName, Vivienne]
-
A.
fullNameRevealed
Indicates that an entity’s complete personal name has been disclosed or made known to another party or in a given context.
-
B.
isPartlyKnownAs
chosen
Indicates that an entity is known by a particular name or label in some, but not all, contexts or sources.
-
C.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
-
D.
notableMemberCommonName
Indicates that the object is the commonly used or well-known name of a notable member associated with the subject.
-
E.
realName
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
- 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_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 7:12 p.m.