Triple
T11167108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ewing Fracture Zone |
E264187
|
entity |
| Predicate | isMajorFeatureOf |
P29386
|
FINISHED |
| Object | Atlantic Ocean seafloor |
—
|
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: Atlantic Ocean seafloor | Statement: [Ewing Fracture Zone, isMajorFeatureOf, Atlantic Ocean seafloor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorFeatureOf Context triple: [Ewing Fracture Zone, isMajorFeatureOf, Atlantic Ocean seafloor]
-
A.
isFeatureOf
chosen
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
B.
isMajorSeeWithin
Indicates that one entity is the primary or most significant location or area encompassed within the boundaries of another entity.
-
C.
isFeatureBased
Indicates that one entity is derived from, determined by, or constructed using the characteristics or attributes of another entity.
-
D.
isMajorStorageFor
Indicates that one entity serves as the primary or main storage location or repository for another entity.
-
E.
isMajorProviderFor
Indicates that one entity serves as a primary or leading supplier or source of goods, services, or resources for 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e88843cc81909e503f0921c6d297 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.