Triple
T26598494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holmes Run |
E667557
|
entity |
| Predicate | nameLikelyDerivedFrom |
P64092
|
FINISHED |
| Object | surname Holmes |
—
|
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: surname Holmes | Statement: [Holmes Run, nameLikelyDerivedFrom, surname Holmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameLikelyDerivedFrom Context triple: [Holmes Run, nameLikelyDerivedFrom, surname Holmes]
-
A.
familyNameDerivedFrom
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
B.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
C.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
D.
possibleNameEtymology
chosen
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
E.
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.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6156db8c081909facff45ff1cda55 |
completed | May 2, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:11 a.m.