Triple
T28016602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon thundereggs |
E707559
|
entity |
| Predicate | innerAppearance |
P143336
|
FINISHED |
| Object | geode-like cavities |
—
|
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: geode-like cavities | Statement: [Oregon thundereggs, innerAppearance, geode-like cavities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innerAppearance Context triple: [Oregon thundereggs, innerAppearance, geode-like cavities]
-
A.
publicAppearance
Indicates that an entity participates in or is present at an event or situation that is open or visible to the general public.
-
B.
coreAppearance
Indicates that one entity serves as the primary or defining visual form or look of another entity.
-
C.
primaryAppearance
Indicates that the referenced entity is the main or most prominent visual or representational form in which another entity is typically depicted or recognized.
-
D.
appearance
Indicates how something looks or seems to an observer, including its visible form, condition, or outward impression.
-
E.
describesAppearanceOf
chosen
Indicates that one entity provides information about the visual characteristics or outward look 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:07 p.m.