Triple
T24637987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMD-103 |
E609865
|
entity |
| Predicate | hasBuilderModel |
P47371
|
FINISHED |
| Object | P40DC |
—
|
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: P40DC | Statement: [AMD-103, hasBuilderModel, P40DC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuilderModel Context triple: [AMD-103, hasBuilderModel, P40DC]
-
A.
builderModel
chosen
Indicates a relationship where one entity serves as the design or construction template (the "builder model") used to create, configure, or generate another entity.
-
B.
hasOrganBuilder
Indicates a relationship where an organ (typically a pipe organ) is associated with the person or company that built it.
-
C.
hasBuilt
Indicates that one entity is the creator or constructor of another entity.
-
D.
hasBuilderPredecessor
Indicates that one builder entity temporally or logically precedes another in a construction or creation process.
-
E.
hasBuildingComponent
Indicates that one entity includes, contains, or is composed of another entity as a physical building component.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:33 a.m.