Triple
T33027091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SipHash-2-4 |
E845070
|
entity |
| Predicate | referenceImplementationLanguage |
P46793
|
FINISHED |
| Object | C |
—
|
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: C | Statement: [SipHash-2-4, referenceImplementationLanguage, C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceImplementationLanguage Context triple: [SipHash-2-4, referenceImplementationLanguage, C]
-
A.
languageOfImplementation
Indicates the programming language in which a given software system, component, or algorithm is implemented.
-
B.
derivationLanguage
Indicates the language from which something (such as a word, term, or expression) is derived.
-
C.
implementedInLanguage
chosen
Indicates that a piece of software or code is written using a particular programming language.
-
D.
languageOfDocumentation
Indicates the language in which the documentation for an entity is written or provided.
-
E.
sharedLanguageStandard
Indicates that the related entities use or conform to the same language standard or specification.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 1:23 a.m.