Triple
T5395941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarshish |
E120653
|
entity |
| Predicate | distanceConnotation |
P5679
|
FINISHED |
| Object | extreme remoteness |
—
|
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: extreme remoteness | Statement: [Tarshish, distanceConnotation, extreme remoteness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceConnotation Context triple: [Tarshish, distanceConnotation, extreme remoteness]
-
A.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
B.
distanceCategory
chosen
Indicates the qualitative classification of how far apart two entities are from each other (e.g., near, medium, far).
-
C.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
D.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
E.
distanceScaleRole
Indicates the role or function that a particular distance scale plays within a measurement, model, or spatial relationship.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.