Triple
T23704235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhiban |
E585673
|
entity |
| Predicate | hasNearbyFind |
P120317
|
FINISHED |
| Object | Mesha Stele |
—
|
NE NERFINISHED |
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: Mesha Stele | Statement: [Dhiban, hasNearbyFind, Mesha Stele]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyFind Context triple: [Dhiban, hasNearbyFind, Mesha Stele]
-
A.
hasNearbyDiscovery
chosen
Indicates that one entity has a discovery located in close physical or spatial proximity to it.
-
B.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
hasNearbySourceOf
Indicates that one entity is located close enough to another entity to serve as a relevant or accessible source of it.
-
E.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b685dfc8819081906aceab7b0bdd |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.