Triple
T31882198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laish |
E813910
|
entity |
| Predicate | distanceDescription |
P5679
|
FINISHED |
| Object | far from Sidon according to Judges 18 |
—
|
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: far from Sidon according to Judges 18 | Statement: [Laish, distanceDescription, far from Sidon according to Judges 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceDescription Context triple: [Laish, distanceDescription, far from Sidon according to Judges 18]
-
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.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
D.
distanceProvidedBy
Indicates that a specific distance value is supplied or made available by a particular source or provider.
-
E.
distancesFrom
Indicates the measured spatial separation between one entity and one or more other entities.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
Created at: April 30, 2026, 11:56 p.m.