Triple
T16211807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brachiopoda |
E393482
|
entity |
| Predicate | shellMicrostructure |
P69499
|
FINISHED |
| Object | lamellar |
—
|
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: lamellar | Statement: [Brachiopoda, shellMicrostructure, lamellar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shellMicrostructure Context triple: [Brachiopoda, shellMicrostructure, lamellar]
-
A.
microscopicStructure
chosen
Indicates the detailed arrangement and organization of components at a microscopic scale within an entity.
-
B.
crystalStructure
Indicates the specific geometric arrangement of atoms or molecules in a crystalline material.
-
C.
hasMicroscopicDynamics
Indicates that one entity exhibits or is characterized by underlying microscopic-level behaviors, processes, or interactions that govern its dynamics.
-
D.
sedimentaryStructure
Indicates a relationship where a geological entity exhibits or is characterized by a particular sedimentary structure formed during deposition or shortly thereafter.
-
E.
typicalStructuralElement
Indicates that one entity is a standard or characteristic structural component commonly found within or forming part 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f1bef8819094e724f5cd0b86d5 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.