Triple
T31882204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laish |
E813910
|
entity |
| Predicate | relatedBiblicalPlaceName |
P3158
|
FINISHED |
| Object | Dan |
E72350
|
NE 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: Dan | Statement: [Laish, relatedBiblicalPlaceName, Dan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedBiblicalPlaceName Context triple: [Laish, relatedBiblicalPlaceName, Dan]
-
A.
nearbyBiblicalSites
Indicates that one or more biblical sites are located close to a given reference location or to each other.
-
B.
biblicalCityName
Indicates that the entity is identified by a name used for a city in the Bible.
-
C.
relatedPlace
chosen
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
D.
relatedMythicalPlace
Indicates that one entity has an association or connection with a mythical or legendary place in relation to the other entity.
-
E.
hasPlaceNamesakeIn
Indicates that something is named after a particular place or location.
- F. None of above.
Provenance (4 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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb132c2788190b7220193f3b49c8c |
completed | June 14, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:56 p.m.