Triple
T38522885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kristin Hudson |
E922537
|
entity |
| Predicate | hasPublicRoleAs |
P161
|
FINISHED |
| Object | Christian marriage mentor |
—
|
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: Christian marriage mentor | Statement: [Kristin Hudson, hasPublicRoleAs, Christian marriage mentor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicRoleAs Context triple: [Kristin Hudson, hasPublicRoleAs, Christian marriage mentor]
-
A.
hasPublicSpaceRole
Indicates that an entity holds a specific role, function, or responsibility within a public space.
-
B.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
C.
hasPublicAuthorityType
Indicates that an entity possesses a specific type or category of public authority status or role.
-
D.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:32 p.m.