Triple
T17565427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nelwyn people |
E427799
|
entity |
| Predicate | usesTechnologyLevel |
P2086
|
FINISHED |
| Object | medieval |
—
|
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: medieval | Statement: [Nelwyn people, usesTechnologyLevel, medieval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTechnologyLevel Context triple: [Nelwyn people, usesTechnologyLevel, medieval]
-
A.
technologyLevel
chosen
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
B.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
C.
technologyLevelComparedTo
Indicates how the technological advancement of one entity compares relative to that of another entity.
-
D.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
E.
inUniverseTechnologyOf
Indicates that a technology exists within, and is part of, the fictional universe or setting associated with a given 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592ce42c8190a54a0a328c5e8ffc |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.