Triple
T1016665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abraham Rycken |
E21944
|
entity |
| Predicate | hasSurnameEtymology |
P3325
|
FINISHED |
| Object | source of the toponym "Rikers 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: source of the toponym "Rikers Island" | Statement: [Abraham Rycken, hasSurnameEtymology, source of the toponym "Rikers Island"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameEtymology Context triple: [Abraham Rycken, hasSurnameEtymology, source of the toponym "Rikers Island"]
-
A.
hasTitleEtymology
Indicates that the origin or derivation of a title is based on, or explained by, another term, name, or linguistic source.
-
B.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
C.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
D.
usedAsSurnameInCountry
Indicates that a particular name functions as a family surname within the specified country.
-
E.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c1e9d08190baf7e81f3777168d |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.