Triple
T32430022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isenburg-Arnfels |
E828693
|
entity |
| Predicate | establishedAsPartitionOf |
P143992
|
FINISHED |
| Object | County of Isenburg |
—
|
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: County of Isenburg | Statement: [Isenburg-Arnfels, establishedAsPartitionOf, County of Isenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsPartitionOf Context triple: [Isenburg-Arnfels, establishedAsPartitionOf, County of Isenburg]
-
A.
partitionOf
chosen
Indicates that one entity represents a subdivision or component segment of another entity, such that together similar entities collectively form the whole.
-
B.
usedToBePartOf
Indicates that an entity was formerly a component or member of another entity but is no longer part of it.
-
C.
establishedAsBranchBy
Indicates that one entity was created or designated as a branch or subsidiary by another entity.
-
D.
foundedAsPartOf
Indicates that an entity was established as a component, division, or subset of a larger existing organization, project, or structure.
-
E.
nowAdministeredAsPartOf
Indicates that something is currently being given or managed as a component of a larger treatment, program, or regimen.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 12:54 a.m.