Triple
T10980238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flentrop organ |
E259483
|
entity |
| Predicate | builderSpecialization |
P54223
|
FINISHED |
| Object | Baroque-style organs |
—
|
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: Baroque-style organs | Statement: [Flentrop organ, builderSpecialization, Baroque-style organs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builderSpecialization Context triple: [Flentrop organ, builderSpecialization, Baroque-style organs]
-
A.
builder
Indicates that an entity is responsible for constructing, creating, or assembling another entity.
-
B.
branchSpecialization
Indicates that one branch or subdivision is specialized or focused in a particular area, function, or domain relative to others.
-
C.
creatorSpecialization
chosen
Indicates the specific field, discipline, or area of expertise in which a creator primarily works or is specialized.
-
D.
builderModel
Indicates a relationship where one entity serves as the design or construction template (the "builder model") used to create, configure, or generate another entity.
-
E.
cargoSpecialization
Indicates that an entity is specialized or designated for handling, transporting, or managing a particular type or category of cargo.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772e97cf88190a65dab3ec4e5f7f3 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.