Triple
T37078063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girl Scout Leadership Experience |
E917764
|
entity |
| Predicate | includesOutcomeArea |
P205710
|
FINISHED |
| Object | Sense of Self |
—
|
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: Sense of Self | Statement: [Girl Scout Leadership Experience, includesOutcomeArea, Sense of Self]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOutcomeArea Context triple: [Girl Scout Leadership Experience, includesOutcomeArea, Sense of Self]
-
A.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
B.
assessmentAreaDefinedBy
Indicates that the scope or domain of an assessment is specified or delimited by a particular area or boundary.
-
C.
includesAreasOff
Indicates that something encompasses or covers areas that are turned off, inactive, or excluded from normal operation.
-
D.
includesAreaType
Indicates that one entity encompasses or contains another entity of a specified area type within its scope or boundaries.
-
E.
includesCapabilityArea
Indicates that one entity encompasses or contains a specific capability area as part of its overall scope or functionality.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.