Triple
T23498720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organ Pipes (Drakensberg) |
E571775
|
entity |
| Predicate | shapeResemblance |
P94757
|
FINISHED |
| Object | church organ pipes |
—
|
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: church organ pipes | Statement: [Organ Pipes (Drakensberg), shapeResemblance, church organ pipes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shapeResemblance Context triple: [Organ Pipes (Drakensberg), shapeResemblance, church organ pipes]
-
A.
faceResemblance
Indicates that one entity’s facial appearance is similar to or resembles that of another entity.
-
B.
morphologicalComparison
Indicates a relationship where two or more entities are compared based on differences or similarities in their morphological (form or structural) characteristics.
-
C.
hasSimilarityTo
chosen
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
D.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
E.
speciesResemblance
Indicates that one species shares notable similarities in appearance or characteristics with another species.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e184ec8190aff3677c9b00a8f2 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:06 p.m.