Triple
T2798921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nye |
E53104
|
entity |
| Predicate | possibleDerivation |
P12825
|
FINISHED |
| Object | Middle English phrase "atten eye" (at the island) |
—
|
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: Middle English phrase "atten eye" (at the island) | Statement: [Nye, possibleDerivation, Middle English phrase "atten eye" (at the island)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleDerivation Context triple: [Nye, possibleDerivation, Middle English phrase "atten eye" (at the island)]
-
A.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
-
B.
derivationType
chosen
Indicates the specific manner or process by which one entity is derived or obtained from another.
-
C.
possibleModel
Indicates that one entity can serve as a potential or candidate model or template for another entity.
-
D.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
E.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddf31eec8190a898713e53d1aa5c |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.