Triple
T9390377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Michael Jackson II |
E226012
|
entity |
| Predicate | keepsPrivateLife |
P62561
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Prince Michael Jackson II, keepsPrivateLife, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keepsPrivateLife Context triple: [Prince Michael Jackson II, keepsPrivateLife, true]
-
A.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
B.
privacyProperty
Indicates that one entity has a characteristic, rule, or condition specifically related to privacy in the context of the relationship.
-
C.
hasPersonalLife
chosen
Indicates that an entity has aspects, activities, or relationships belonging to its private or non-professional life.
-
D.
keptLowPublicProfile
Indicates that an entity deliberately maintained minimal visibility or attention in public or media contexts.
-
E.
privacyCharacteristic
Indicates the specific privacy-related property or feature that characterizes how information is handled, protected, or exposed in a given context.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd510d7a9c8190a74ccdb5478dedc9 |
completed | April 1, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.