Triple
T22693164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDR41 |
E561101
|
entity |
| Predicate | hasRepeatType |
P10543
|
FINISHED |
| Object | WD40 repeat |
—
|
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: WD40 repeat | Statement: [WDR41, hasRepeatType, WD40 repeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepeatType Context triple: [WDR41, hasRepeatType, WD40 repeat]
-
A.
hasRepetition
Indicates that something occurs, appears, or is performed more than once, showing recurrence or repeated instances within a given context.
-
B.
usesRepetition
Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
-
C.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
-
D.
hasRecurringElement
chosen
Indicates that an entity includes an element that appears repeatedly or occurs multiple times within it.
-
E.
repetitionPattern
Indicates a recurring structure or sequence in which an action, event, or element is repeated over time or across instances.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789c6ae481908975b7d27e7624ac |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.