Triple
T15473355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arka Gdynia |
E376719
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Arka |
E376719
|
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: Arka | Statement: [Arka Gdynia, shortName, Arka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arka Context triple: [Arka Gdynia, shortName, Arka]
-
A.
Arka
chosen
Arka is a Polish sports club best known for its professional football team based in the port city of Gdynia.
-
B.
Arki
Arki is a small town in the Solan district of Himachal Pradesh, India, known for its historic fort and scenic Himalayan surroundings.
-
C.
Arki
Arki is a small, sparsely populated Greek island in the Aegean Sea, known for its quiet beaches and traditional fishing community.
-
D.
Ara
Ara is a historic city in the Indian state of Bihar, known for its role in the Indian independence movement and as the center of Bhojpur district.
-
E.
Ara
Ara is a small southern sky constellation named after the altar, located near the Milky Way and visible primarily from the Southern Hemisphere.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6c57308190b4cfe661c26addd4 |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2d075e64819097061ef4c205577e |
completed | May 9, 2026, 12:48 p.m. |
Created at: April 10, 2026, 3:33 a.m.