Triple
T15673199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gutenberg discontinuity |
E377370
|
entity |
| Predicate | locatedAtDepth |
P8582
|
FINISHED |
| Object | approximately 2900 kilometers |
—
|
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: approximately 2900 kilometers | Statement: [Gutenberg discontinuity, locatedAtDepth, approximately 2900 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtDepth Context triple: [Gutenberg discontinuity, locatedAtDepth, approximately 2900 kilometers]
-
A.
maxDepthLocation
Indicates the location at which the maximum depth of something (e.g., an object, structure, or feature) is reached or measured.
-
B.
reachedDepth
chosen
Indicates that an entity has arrived at or attained a specified depth level in some medium or context.
-
C.
positionAt
Indicates that one entity is located at, or occupies, a specific spatial position relative to another entity or reference frame.
-
D.
locatedOnLevel
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
-
E.
locatedAtBaseOf
Indicates that one entity is positioned at or near the bottom or lowest supporting part 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2c996c8190a9ebe0e92608feaa |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.