Triple
T28873109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glove Capital of the World |
E732185
|
entity |
| Predicate | scopeOfClaim |
P74239
|
FINISHED |
| Object | worldwide prominence in glove manufacturing |
—
|
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: worldwide prominence in glove manufacturing | Statement: [Glove Capital of the World, scopeOfClaim, worldwide prominence in glove manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfClaim Context triple: [Glove Capital of the World, scopeOfClaim, worldwide prominence in glove manufacturing]
-
A.
scopeClaim
chosen
Indicates that a claim or statement applies within a specified scope, context, or boundary.
-
B.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
C.
causeOfClaim
Indicates the underlying reason, event, or condition that gives rise to a particular claim.
-
D.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
E.
scopeOfAdvice
Indicates that one entity defines or specifies the range, boundaries, or subject matter covered by another entity’s advice or guidance.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4842588190835ef304e918d03a |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:34 a.m.