Triple
T10430224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geir |
E245892
|
entity |
| Predicate | nameElement |
P27866
|
FINISHED |
| Object | geirr |
E245892
|
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: geirr | Statement: [Geir, nameElement, geirr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: geirr Context triple: [Geir, nameElement, geirr]
-
A.
gez
gez is the ISO 639-3 code for Geʽez, an ancient Semitic language of Ethiopia that serves as the liturgical language of the Ethiopian and Eritrean Orthodox churches.
-
B.
Geir
chosen
Geir is a masculine given name of Old Norse origin, commonly used in Scandinavian countries and meaning "spear."
-
C.
Geg
Geg is an alternative name for Gheg, the northern dialect group of the Albanian language spoken primarily in northern Albania and surrounding regions.
-
D.
Ger
Ger is a prominent Hasidic dynasty, originating in Góra Kalwaria, Poland, known for its large following and significant influence within the Haredi Jewish world.
-
E.
Geirröd
Geirröd is a fearsome giant from Norse mythology, best known for luring the god Thor into a deadly trap in his hall in Jotunheim.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea62d6448190a7f5b785467824cf |
completed | April 7, 2026, 11:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87eb068bc8190be9c7c916850278e |
completed | April 10, 2026, 4:38 a.m. |
Created at: April 6, 2026, 12:13 p.m.