Triple
T10148034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberstleutnant |
E231753
|
entity |
| Predicate | typicalAddressForm |
P4477
|
FINISHED |
| Object | Herr Oberstleutnant |
—
|
LITERAL 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: Herr Oberstleutnant | Statement: [Oberstleutnant, typicalAddressForm, Herr Oberstleutnant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAddressForm Context triple: [Oberstleutnant, typicalAddressForm, Herr Oberstleutnant]
-
A.
addressFormFor
chosen
Indicates the form of address or mode of speaking that one entity should use when referring to or speaking to another entity.
-
B.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
C.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
D.
traditionalAddress
Indicates that one entity is the conventional or customary form of address (e.g., title, honorific, or name) used for referring to another entity.
-
E.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
- F. None of above.
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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec011c24819089b456fc8b9ed80c |
completed | April 2, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:08 p.m.