Triple
T35521566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Boy and the Filberts |
E1026562
|
entity |
| Predicate | hasAdviserCharacter |
P178562
|
FINISHED |
| Object | an older person |
—
|
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: an older person | Statement: [The Boy and the Filberts, hasAdviserCharacter, an older person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdviserCharacter Context triple: [The Boy and the Filberts, hasAdviserCharacter, an older person]
-
A.
hasAdvising
Indicates that one entity provides guidance, counseling, or advisory support to another entity.
-
B.
advisorOf
Indicates that one entity serves as an advisor, providing guidance or counsel, to another entity.
-
C.
typeOfAdviser
chosen
Indicates the specific advisory role or category that an adviser holds in relation to another entity.
-
D.
hasCoachCharacter
Indicates that one entity serves as the coach or trainer character associated with another entity.
-
E.
hasEnforcerCharacter
Indicates that an entity includes or is associated with a character who acts as an enforcer, carrying out enforcement or coercive roles on its behalf.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4:04 p.m.