Triple
T11296057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girl Scout Daisy |
E267454
|
entity |
| Predicate | usesProgramElement |
P3097
|
FINISHED |
| Object | Daisy petals |
—
|
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: Daisy petals | Statement: [Girl Scout Daisy, usesProgramElement, Daisy petals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProgramElement Context triple: [Girl Scout Daisy, usesProgramElement, Daisy petals]
-
A.
hasProgramElement
Indicates that one entity contains, includes, or is associated with a specific program element (such as a function, class, module, or code component).
-
B.
usedByProgram
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
-
C.
usedProgramModel
Indicates that an entity employed a specific program model as the basis or framework for its activities or operations.
-
D.
usesElement
chosen
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
E.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a262e08190a7c1eacbc6019496 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.