Triple
T31329856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naxian marble |
E798993
|
entity |
| Predicate | mainConstituent |
P130659
|
FINISHED |
| Object | calcite |
—
|
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: calcite | Statement: [Naxian marble, mainConstituent, calcite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainConstituent Context triple: [Naxian marble, mainConstituent, calcite]
-
A.
majorConstituent
chosen
Indicates that one entity is a primary or dominant component or part of another entity.
-
B.
majorConstituentType
Indicates the type or category of a primary or dominant component that makes up a larger whole.
-
C.
hasPrimaryConstituent
Indicates that one entity serves as the main or principal component, ingredient, or element of another entity.
-
D.
dominantConstituentState
Indicates that one constituent state holds a primary or controlling position relative to other constituent states within a larger political or organizational structure.
-
E.
secondaryConstituent
Indicates that one entity functions as a secondary or subordinate component, element, or member within the structure or composition of 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 29, 2026, 9:16 p.m.