Triple
T14966340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encke (lunar crater) |
E373197
|
entity |
| Predicate | hasInteriorCharacteristic |
P6655
|
FINISHED |
| Object | relatively shallow floor |
—
|
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: relatively shallow floor | Statement: [Encke (lunar crater), hasInteriorCharacteristic, relatively shallow floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorCharacteristic Context triple: [Encke (lunar crater), hasInteriorCharacteristic, relatively shallow floor]
-
A.
hasInteriorFeature
chosen
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
hasInteriorColor
Indicates that an entity possesses a specific color used on its interior surfaces or internal parts.
-
C.
hasRichInteriorDecoration
Indicates that an entity features elaborate, ornate, or luxuriously detailed interior decoration.
-
D.
hasInteriorBehavior
Indicates that an entity exhibits a particular behavior or set of behaviors within its internal or enclosed space.
-
E.
interiorStyle
Indicates that one entity has a particular interior design style or aesthetic characterized by the other 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e2fdcc8190bffe603db3388736 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:47 a.m.