Triple
T16171469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grange |
E392446
|
entity |
| Predicate | derivedFromCommonNoun |
P99154
|
FINISHED |
| Object | grange (meaning barn or granary) |
—
|
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: grange (meaning barn or granary) | Statement: [Grange, derivedFromCommonNoun, grange (meaning barn or granary)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromCommonNoun Context triple: [Grange, derivedFromCommonNoun, grange (meaning barn or granary)]
-
A.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
derivedFromLexeme
chosen
Indicates that one linguistic form or expression originates from, or is morphologically or semantically based on, a particular lexeme.
-
C.
nounFormOf
Indicates that one term is the noun form derived from, or corresponding to, another term (typically a verb or adjective).
-
D.
isAlsoCommonNounInLanguage
Indicates that an entity is also used as a common noun in a specified language.
-
E.
typicalWordFormation
Indicates the usual or most common way in which a word is formed from other linguistic elements (such as roots, affixes, or compounds).
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb7ab1481908fc35bfc8c56e5f2 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.