Triple
T5899691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingeborg |
E131189
|
entity |
| Predicate | etymologyComponent |
P506
|
FINISHED |
| Object | Ing |
E515676
|
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: Ing | Statement: [Ingeborg, etymologyComponent, Ing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ing Context triple: [Ingeborg, etymologyComponent, Ing]
-
A.
Ing
chosen
Ing is a shortened form or nickname derived from the given name Ingrid.
-
B.
GIN
GIN is the three-letter ISO 3166-1 alpha-3 country code assigned to the West African nation of Guinea.
-
C.
Ins
Ins is a small Swiss municipality located in the Seeland region of the canton of Bern, known for its agricultural landscape and proximity to the lakes of Biel, Neuchâtel, and Murten.
-
D.
IG
IG is the commonly used abbreviation for the Irish Guards, an infantry regiment of the British Army known for its ceremonial duties and operational deployments.
-
E.
Ng
Ng is a common Chinese surname found across various Chinese-speaking communities and the diaspora, often representing the Cantonese or Hokkien romanization of the character 吳 (Wu).
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0373320cc8190bfdb2b09236f55a5 |
completed | March 22, 2026, 6:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b15df86481908b59717b9de63655 |
completed | March 23, 2026, 3:19 a.m. |
Created at: March 22, 2026, 3:58 p.m.