Triple
T13317023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BUNCH |
E317211
|
entity |
| Predicate | terminologyType |
P5567
|
FINISHED |
| Object | industry nickname |
—
|
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: industry nickname | Statement: [BUNCH, terminologyType, industry nickname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminologyType Context triple: [BUNCH, terminologyType, industry nickname]
-
A.
termType
chosen
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
B.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
-
C.
typicalTerm
Indicates that something is a standard, representative, or characteristic term typically associated with a given concept or context.
-
D.
languageTerm
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
-
E.
terminologyNote
Indicates that there is an explanatory note or comment clarifying the use, meaning, or nuances of a specific term in the relationship.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.