Triple
T11296049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girl Scout Daisy |
E267454
|
entity |
| Predicate | followsLevel |
P98366
|
FINISHED |
| Object | Girl Scout pre-membership age |
—
|
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: Girl Scout pre-membership age | Statement: [Girl Scout Daisy, followsLevel, Girl Scout pre-membership age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsLevel Context triple: [Girl Scout Daisy, followsLevel, Girl Scout pre-membership age]
-
A.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
B.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
C.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
D.
followsUnit
Indicates that one unit comes directly after or is ordered subsequent to another unit in a sequence or structure.
-
E.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
- 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_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. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.