Triple
T21689502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerson family |
E535320
|
entity |
| Predicate | hasFamilyProfessionTradition |
P104544
|
FINISHED |
| Object | clergy |
—
|
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: clergy | Statement: [Emerson family, hasFamilyProfessionTradition, clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyProfessionTradition Context triple: [Emerson family, hasFamilyProfessionTradition, clergy]
-
A.
hasOccupationTradition
chosen
Indicates that an entity is associated with a customary or historically established occupation or professional role.
-
B.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
C.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
D.
hasFamilyTrait
Indicates that a particular trait or characteristic is shared among members of the same family or lineage.
-
E.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96ce2ff88190a6cbfff45bb6a04f |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.