Triple
T34922840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VISOR |
E1007193
|
entity |
| Predicate | replacesSense |
P195703
|
FINISHED |
| Object | normal human vision |
—
|
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: normal human vision | Statement: [VISOR, replacesSense, normal human vision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesSense Context triple: [VISOR, replacesSense, normal human vision]
-
A.
replacesConcept
Indicates that one concept takes the place of, or supersedes, another concept in a given context or system.
-
B.
replacesWord
Indicates that one word is substituted for another word in a given context or expression.
-
C.
replacement
Indicates that one entity takes the place of, or is substituted for, another entity in a given context.
-
D.
replacedDefinitionOf
Indicates that one definition or description has been superseded and taken the place of another.
-
E.
replacesOrAlternativesTo
Indicates that one entity serves as a substitute for, or an alternative option to, another entity, potentially taking its place or offering a different choice.
- F. None of above. chosen
Provenance (4 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69fddf70ab10819088b76bd98e208354 |
completed | May 8, 2026, 1:04 p.m. |
Created at: May 3, 2026, 4 p.m.