Triple
T19643712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oort (lunar crater) |
E471609
|
entity |
| Predicate | outerWallCondition |
P136804
|
FINISHED |
| Object | heavily worn by subsequent impacts |
—
|
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: heavily worn by subsequent impacts | Statement: [Oort (lunar crater), outerWallCondition, heavily worn by subsequent impacts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outerWallCondition Context triple: [Oort (lunar crater), outerWallCondition, heavily worn by subsequent impacts]
-
A.
hasOuterWall
Indicates that one entity possesses or is surrounded by an external enclosing wall that defines its outer boundary.
-
B.
boundaryCondition
Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
-
C.
outerSurface
Indicates that one entity forms the external boundary or outermost layer of another entity.
-
D.
potentialSurfaceConditions
Indicates the possible environmental or physical conditions that could exist on a surface under given circumstances or assumptions.
-
E.
bodyWall
Indicates that one entity serves as the body wall or outer structural boundary enclosing another entity.
- F. None of above. chosen
Provenance (4 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641239ca08190a8bb8854f21ab562 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.