Triple
T11296075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girl Scout Daisy |
E267454
|
entity |
| Predicate | uniformIncludes |
P1393
|
FINISHED |
| Object | Daisy tunic or vest |
—
|
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 tunic or vest | Statement: [Girl Scout Daisy, uniformIncludes, Daisy tunic or vest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniformIncludes Context triple: [Girl Scout Daisy, uniformIncludes, Daisy tunic or vest]
-
A.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
outputIncludes
Indicates that the result or product of a process, function, or action contains or incorporates a specified element or component.
-
C.
traditionallyIncludes
Indicates that something customarily or historically contains or incorporates something else as a standard or expected part.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
- 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.