Triple
T12582015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobbit |
E300360
|
entity |
| Predicate | inUniverseTrait |
P74769
|
FINISHED |
| Object | good at moving quietly |
—
|
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: good at moving quietly | Statement: [Hobbit, inUniverseTrait, good at moving quietly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseTrait Context triple: [Hobbit, inUniverseTrait, good at moving quietly]
-
A.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
B.
inUniverseProperty
chosen
Indicates that a property, attribute, or characteristic exists specifically within the context or canon of a particular fictional universe.
-
C.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
D.
inUniverseSpecialization
Indicates that an entity’s specialization or area of focus exists specifically within the context or canon of a particular fictional universe.
-
E.
inUniverseOrigin
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:02 p.m.