Triple
T10898902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shammar |
E257381
|
entity |
| Predicate | spreadTo |
P9468
|
FINISHED |
| Object | Jordan |
E11658
|
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: Jordan | Statement: [Shammar, spreadTo, Jordan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jordan Context triple: [Shammar, spreadTo, Jordan]
-
A.
Jordan
chosen
Jordan is a Middle Eastern country located at the crossroads of Asia, Africa, and Europe, known for its ancient archaeological sites like Petra and its strategic political role in the region.
-
B.
Jordan
Jordan is a municipality in the Philippines that serves as the capital of the island province of Guimaras in the Western Visayas region.
-
C.
Jordan
Jordan is a common given name used by people of all genders in many English-speaking and other countries.
-
D.
Jordan
Jordan was a Formula One racing team and constructor known for launching the careers of several top drivers and competing in the sport during the 1990s and early 2000s.
-
E.
Jordan
Jordan is a scientist known for formally describing the bacterial genus Bradyrhizobium.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a2392c8190bc2c2359d63eff7a |
completed | April 9, 2026, 8:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e154cc97f88190aef41d18b5ebe836 |
completed | April 16, 2026, 9:29 p.m. |
Created at: April 8, 2026, 9:21 p.m.