Triple
T26275355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charley Pearl |
E660551
|
entity |
| Predicate | lifeStatusAtStart |
P160191
|
FINISHED |
| Object | privileged bachelor lifestyle |
—
|
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: privileged bachelor lifestyle | Statement: [Charley Pearl, lifeStatusAtStart, privileged bachelor lifestyle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeStatusAtStart Context triple: [Charley Pearl, lifeStatusAtStart, privileged bachelor lifestyle]
-
A.
lifeStatus
Indicates the current state of an entity’s existence, such as whether it is alive, dead, or in another defined life condition.
-
B.
isUnemployedAtStartOf
Indicates that an individual is unemployed at the beginning of a specified time period or event.
-
C.
lifeStage
Indicates the specific phase or period in an entity’s development or lifecycle that it is currently in.
-
D.
lifeStageAtDeath
Indicates the life stage or age category an entity was in at the time of its death.
-
E.
hasLifetimeStatus
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e33c5748190abaa09d9b0c4c00a |
completed | May 2, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 9:55 p.m.