Triple
T25141472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DA |
E629812
|
entity |
| Predicate | indicatesRegistrationAuthority |
P108933
|
FINISHED |
| Object | city of Darmstadt |
—
|
NE NERFINISHED |
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: city of Darmstadt | Statement: [DA, indicatesRegistrationAuthority, city of Darmstadt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesRegistrationAuthority Context triple: [DA, indicatesRegistrationAuthority, city of Darmstadt]
-
A.
hasRegistrationAuthority
chosen
Indicates that an entity is formally overseen, recorded, or certified by a specific authority responsible for its registration.
-
B.
issuingAuthorityText
Indicates the textual name or description of the authority responsible for issuing a document, credential, or official item.
-
C.
recognizesAuthority
Indicates that one entity accepts, acknowledges, or submits to the power, control, or legitimate decision-making role of another entity.
-
D.
indicatesIssuer
Indicates that one entity serves as the issuer or originator of another entity, such as a document, credential, or financial instrument.
-
E.
identifiesRegistrationLocation
Indicates that an entity specifies the place or jurisdiction where a registration is or should be recorded.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46848ed708190b72d8d7cb252e502 |
completed | May 1, 2026, 8:46 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:29 a.m.