Triple
T27521435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDS |
E694715
|
entity |
| Predicate | registrationAuthorityState |
P162674
|
FINISHED |
| Object | Brandenburg |
—
|
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: Brandenburg | Statement: [LDS, registrationAuthorityState, Brandenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationAuthorityState Context triple: [LDS, registrationAuthorityState, Brandenburg]
-
A.
registrationAuthorityLocatedIn
chosen
Indicates that the authority responsible for registration is situated within a specified geographic or jurisdictional location.
-
B.
registrationAuthorityCountry
Indicates the country that serves as the official authority responsible for registering the entity.
-
C.
hasRegistrationAuthority
Indicates that an entity is formally overseen, recorded, or certified by a specific authority responsible for its registration.
-
D.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
-
E.
issuerState
Indicates the state or jurisdiction that has issued or authorized the referenced entity (such as a document, license, or instrument).
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:21 p.m.