Triple
T11296343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Award |
E267460
|
entity |
| Predicate | projectLeadershipRequirement |
P27972
|
FINISHED |
| Object | girl-led |
—
|
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-led | Statement: [Silver Award, projectLeadershipRequirement, girl-led]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectLeadershipRequirement Context triple: [Silver Award, projectLeadershipRequirement, girl-led]
-
A.
teamLead
Indicates that one entity serves as the leader or primary coordinator of a team that includes the other entity.
-
B.
workRequirement
Indicates that one entity imposes or specifies a condition related to work that another entity must fulfill.
-
C.
hasProfessionalRequirement
Indicates that one entity imposes or specifies a professional qualification, credential, or condition that must be met by another entity.
-
D.
requiresLeaderQualification
Indicates that an entity can only assume or perform a leadership role if a specified qualification or credential is met.
-
E.
rosterRequirement
chosen
Indicates that one entity specifies or imposes a required composition, number, or type of participants that must be included in another entity’s roster.
- 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.