Triple
T20370025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunting Hollow entrance |
E497026
|
entity |
| Predicate | relativeUsageLevel |
P85306
|
FINISHED |
| Object | lesser-used |
—
|
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: lesser-used | Statement: [Hunting Hollow entrance, relativeUsageLevel, lesser-used]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeUsageLevel Context triple: [Hunting Hollow entrance, relativeUsageLevel, lesser-used]
-
A.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
-
B.
hasUsageLevel
chosen
Indicates the degree or intensity with which something is used or utilized.
-
C.
representedLevel
Indicates that one entity denotes or encodes the degree, intensity, or value (i.e., the level) of another entity or property.
-
D.
comparisonLevel
Indicates the degree or intensity to which two or more entities are being compared within a given context.
-
E.
lowerLevelUsedFor
Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6787454a88190ae87d9b3c9b5ad27 |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:26 a.m.