Triple
T32191480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cayuga Productions |
E822265
|
entity |
| Predicate | basedOnNameOrigin |
P3325
|
FINISHED |
| Object | Cayuga Lake |
—
|
NE NERFINISHED |
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: Cayuga Lake | Statement: [Cayuga Productions, basedOnNameOrigin, Cayuga Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnNameOrigin Context triple: [Cayuga Productions, basedOnNameOrigin, Cayuga Lake]
-
A.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
nameOriginExplanation
Indicates that an explanation is provided for the origin or derivation of a given name.
-
C.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
D.
basedOnName
Indicates that one entity is derived, determined, or identified using the name of another entity.
-
E.
characterNameOrigin
Indicates the source or inspiration from which a character’s name is derived.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 1, 2026, 12:35 a.m.