Triple
T38447867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huorns |
E906687
|
entity |
| Predicate | taxonomyInLore |
P99966
|
FINISHED |
| Object | intermediate between Ents and ordinary trees |
—
|
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: intermediate between Ents and ordinary trees | Statement: [Huorns, taxonomyInLore, intermediate between Ents and ordinary trees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonomyInLore Context triple: [Huorns, taxonomyInLore, intermediate between Ents and ordinary trees]
-
A.
taxonomyInGame
Indicates that an entity is classified within a particular taxonomic category as it appears or is represented in a game.
-
B.
categoryInTheology
Indicates that something belongs to, is classified within, or pertains to a particular category or domain in theology.
-
C.
loreType
chosen
Indicates the category or kind of lore that characterizes or classifies a given entity or subject.
-
D.
taxonomicUsage
Indicates the way a taxonomic name is applied or used in a particular context, such as in a classification, identification, or reference.
-
E.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.