Triple
T8200493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyalty Ridge |
E191557
|
entity |
| Predicate | likelyPartOf |
P52847
|
FINISHED |
| Object | submarine plateau system |
—
|
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: submarine plateau system | Statement: [Loyalty Ridge, likelyPartOf, submarine plateau system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyPartOf Context triple: [Loyalty Ridge, likelyPartOf, submarine plateau system]
-
A.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
B.
isNotPartOf
Indicates that one entity does not belong to, is not contained within, and is not a component or member of another entity.
-
C.
consideredPartOf
chosen
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
-
D.
movementPartOf
Indicates that a movement or motion event is a component or segment of a larger, encompassing movement or motion event.
-
E.
partOfType
Indicates that one entity represents a component, segment, or subset that belongs to or is included within the type or category represented by 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df565dc819099537fc06b694b40 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.