Triple
T33185961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashlie Walker |
E849468
|
entity |
| Predicate | public profile |
P5387
|
FINISHED |
| Object | largely private life |
—
|
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: largely private life | Statement: [Ashlie Walker, public profile, largely private life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: public profile Context triple: [Ashlie Walker, public profile, largely private life]
-
A.
publicProfile
chosen
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
B.
profile
Indicates that one entity creates, presents, or analyzes a detailed description or representation of another entity’s characteristics or behavior.
-
C.
profileType
Indicates the specific category or role classification assigned to a profile within a system.
-
D.
profileDirectory
Indicates the directory path where a user's or application's profile data is stored or managed.
-
E.
participantProfile
Indicates that an entity serves as the profile or descriptive record associated with a particular participant in an event, activity, or process.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: May 1, 2026, 1:29 a.m.