Triple
T11478060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girl Scout Bronze Award |
E272072
|
entity |
| Predicate | minimumTeamSize |
P81510
|
FINISHED |
| Object | at least 4 Girl Scouts recommended |
—
|
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: at least 4 Girl Scouts recommended | Statement: [Girl Scout Bronze Award, minimumTeamSize, at least 4 Girl Scouts recommended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumTeamSize Context triple: [Girl Scout Bronze Award, minimumTeamSize, at least 4 Girl Scouts recommended]
-
A.
minimumNumberOfMembers
Indicates the smallest allowable or required number of members that must be present or involved in a given context or group.
-
B.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
-
C.
minimumUnitSize
Indicates that there is a smallest allowable or defined size or quantity for the unit involved in the relationship.
-
D.
recommendedMinimumSize
chosen
Indicates the smallest size that is advised or suggested as a minimum for something to be used or considered appropriate.
-
E.
collaborationSize
Indicates the number of participants involved together in a given collaborative relationship or activity.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294e0fe08190b018e840146e27ca |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.