Triple
T33240607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | guardians of the Shire |
E850951
|
entity |
| Predicate | isUnknownTo |
P148132
|
FINISHED |
| Object | the Shire-hobbits generally |
—
|
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: the Shire-hobbits generally | Statement: [guardians of the Shire, isUnknownTo, the Shire-hobbits generally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnknownTo Context triple: [guardians of the Shire, isUnknownTo, the Shire-hobbits generally]
-
A.
hasUnknown
Indicates that an entity possesses or is associated with information, attributes, or values that are not known or not specified.
-
B.
unknownFor
chosen
Indicates that some information, value, or property about one entity is not known or not determined with respect to another entity.
-
C.
ignorantOf
Indicates that one entity lacks knowledge or awareness of another entity or of some specific fact, topic, or situation.
-
D.
knownToBe
Indicates that one entity is recognized or acknowledged as being a certain way, having a certain property, or fitting a particular description by others.
-
E.
isLessKnownFor
Indicates that one entity is recognized or associated with something to a lesser degree than another entity is.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.