Triple
T30151401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naughty and Nice list |
E766405
|
entity |
| Predicate | maintainedWithHelpFrom |
P27376
|
FINISHED |
| Object | elves |
—
|
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: elves | Statement: [Naughty and Nice list, maintainedWithHelpFrom, elves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedWithHelpFrom Context triple: [Naughty and Nice list, maintainedWithHelpFrom, elves]
-
A.
legacyMaintainedBy
Indicates that responsibility for preserving, continuing, or upholding a legacy rests with a particular entity.
-
B.
partlyMaintainedBy
chosen
Indicates that an entity is only partially supported, serviced, or kept in working order by another entity, rather than being fully maintained by it.
-
C.
oftenMaintainedBy
Indicates that something is regularly or frequently kept in working order, cared for, or updated by a particular agent or entity.
-
D.
maintainedAs
Indicates that one entity is kept in a particular state, condition, or configuration by another entity through ongoing care, management, or support.
-
E.
maintainedFor
Indicates that something is kept in a particular state, condition, or operation for the benefit, use, or purpose of 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 7:20 p.m.