Triple
T28181326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thornton |
E716034
|
entity |
| Predicate | derivedFromOldEnglishElements |
P506
|
FINISHED |
| Object | thorn |
—
|
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: thorn | Statement: [Thornton, derivedFromOldEnglishElements, thorn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromOldEnglishElements Context triple: [Thornton, derivedFromOldEnglishElements, thorn]
-
A.
derivedFromEarlierEnglishName
Indicates that one name originates from or is historically developed out of an earlier English name.
-
B.
nameInOldEnglish
Indicates that an entity’s name is given or represented in the Old English language.
-
C.
traditionalEtymology
Indicates that an entity’s origin or meaning is explained according to a historically established or customary etymological account.
-
D.
etymologicalForm
Indicates that one linguistic form is derived from, or historically originates in, another form as its etymological source.
-
E.
etymologicalLanguage
chosen
Indicates the language from which a word or term is historically derived in its etymology.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 10:19 p.m.