Triple
T4592299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnhemmer |
E103520
|
entity |
| Predicate | hasTypeOfIdentity |
P40349
|
FINISHED |
| Object | local identity |
—
|
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: local identity | Statement: [Arnhemmer, hasTypeOfIdentity, local identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfIdentity Context triple: [Arnhemmer, hasTypeOfIdentity, local identity]
-
A.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
B.
hasIdentityComponent
chosen
Indicates that an entity includes or is associated with a specific component that contributes to or defines its identity.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
E.
hasTypeOfCase
Indicates that an entity is associated with or classified under a particular type or category of case.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd592520ec8190b1bd4cb4d9b94c94 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:11 p.m.