Triple
T32041296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilderness Explorer uniform |
E818225
|
entity |
| Predicate | badgeCount |
P173501
|
FINISHED |
| Object | many merit badges |
—
|
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: many merit badges | Statement: [Wilderness Explorer uniform, badgeCount, many merit badges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: badgeCount Context triple: [Wilderness Explorer uniform, badgeCount, many merit badges]
-
A.
badgeUsage
Indicates how and in what context a badge is applied, displayed, or utilized in relation to an entity or activity.
-
B.
bookmarkCount
Indicates the number of times an item has been bookmarked by users.
-
C.
badgeVariesBy
Indicates that the characteristics or appearance of a badge change depending on some varying condition, context, or parameter.
-
D.
badge
Indicates that one entity confers, displays, or is associated with a symbolic mark or emblem representing status, achievement, role, or affiliation in relation to another entity.
-
E.
badgeText
Indicates that a visual badge or label is associated with an entity, displaying specific text content.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:19 a.m.