Triple
T560924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nell |
E13447
|
entity |
| Predicate | semanticOrigin |
P409
|
FINISHED |
| Object | often ultimately from Greek Helene |
—
|
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: often ultimately from Greek Helene | Statement: [Nell, semanticOrigin, often ultimately from Greek Helene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticOrigin Context triple: [Nell, semanticOrigin, often ultimately from Greek Helene]
-
A.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
B.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
C.
semanticType
Indicates that something belongs to or is categorized under a particular semantic class or type based on its meaning.
-
D.
collectionOrigin
Indicates that one entity is the source, provenance, or originating context from which a collection of items or data has been derived or assembled.
-
E.
sourceLanguageMeaning
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
- 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.