Triple
T560930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nell |
E13447
|
entity |
| Predicate | hasHistoricalUsageSince |
P2451
|
FINISHED |
| Object | at least the Middle Ages in English |
—
|
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: at least the Middle Ages in English | Statement: [Nell, hasHistoricalUsageSince, at least the Middle Ages in English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalUsageSince Context triple: [Nell, hasHistoricalUsageSince, at least the Middle Ages in English]
-
A.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
B.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
-
C.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
D.
inUseSince
chosen
Indicates that an entity has been actively in use starting from a specified point in time.
-
E.
historicallyRecordedSince
Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499e2795c8190903240e79964156d |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494befb8481908bb4e2e9f31e343b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.