Triple
T8092865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teutonic Order state |
E188909
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | mark |
E610681
|
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: mark | Statement: [Teutonic Order state, currency, mark]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: mark Context triple: [Teutonic Order state, currency, mark]
-
A.
Marker
Marker is a rural municipality in Viken county, southeastern Norway, known for its forests, lakes, and location near the Swedish border.
-
B.
Marks
Marks is a surname of English and Jewish origin borne by various notable individuals across fields such as sports, politics, and the arts.
-
C.
Mark
chosen
The Mark was the basic unit of currency used in Germany during various historical periods, including the era of the Papiermark.
-
D.
Mark
Mark is a punctuation symbol used in writing systems, including those that employ the Cyrillic Extended-B Unicode block.
-
E.
Mark
Mark is a common masculine given name of Latin origin, derived from Marcus and historically associated with figures such as the evangelist Saint Mark.
- 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4222b68c81909c8bc326763240d0 |
completed | March 31, 2026, 3:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc64112138819096050975d707d8ee |
completed | April 1, 2026, 12:17 a.m. |
Created at: March 30, 2026, 5:30 p.m.