Triple
T474227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia marble |
E9024
|
entity |
| Predicate | industryAssociatedWith |
P6744
|
FINISHED |
| Object | Georgia marble industry |
—
|
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: Georgia marble industry | Statement: [Georgia marble, industryAssociatedWith, Georgia marble industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryAssociatedWith Context triple: [Georgia marble, industryAssociatedWith, Georgia marble industry]
-
A.
industryOfUnderlyingCompany
chosen
Indicates the industry sector in which the underlying company associated with this entity operates.
-
B.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
C.
industryCenter
Indicates that a location functions as a primary hub or focal point for industrial activity or production.
-
D.
foundingIndustry
Indicates the industry or sector in which an entity was originally founded or began its primary operations.
-
E.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f039f3d88190a7c93ecbf1bf5f58 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edeed31881908cf43beed410572d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.