Triple
T10555978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander John Buckley Ford |
E249086
|
entity |
| Predicate | hasPrivacyStatus |
P15698
|
FINISHED |
| Object | highly 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: highly private life | Statement: [Alexander John Buckley Ford, hasPrivacyStatus, highly private life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrivacyStatus Context triple: [Alexander John Buckley Ford, hasPrivacyStatus, highly private life]
-
A.
hasPublicAccessRestrictions
Indicates that there are specific limitations or conditions governing public access to the associated resource or entity.
-
B.
hasProprietaryStatus
Indicates that something is owned, controlled, or protected as proprietary rather than being public or freely available.
-
C.
privacyProperty
chosen
Indicates that one entity has a characteristic, rule, or condition specifically related to privacy in the context of the relationship.
-
D.
hasPolicyStatus
Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
-
E.
isPrivateOrPublic
Indicates whether something is designated as private or public in terms of its accessibility or visibility.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52712a9988190bf63e7c47f6e6fc1 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.