Triple
T29325963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English horn |
E743643
|
entity |
| Predicate | hasTypicalTransposition |
P194464
|
FINISHED |
| Object | in F |
—
|
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: in F | Statement: [English horn, hasTypicalTransposition, in F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalTransposition Context triple: [English horn, hasTypicalTransposition, in F]
-
A.
requiresTranspositionBy
Indicates that one entity must be transposed or shifted (such as in position, order, or key) by another entity in order to be correctly interpreted or used.
-
B.
isGeneratedByTranspositions
Indicates that one entity is produced from another by applying one or more transposition operations (i.e., swapping positions of elements).
-
C.
canTransposeFrom
Indicates that one entity is able to be transposed or converted from the form, structure, or representation of another entity.
-
D.
is3TranspositionGroup
Indicates that the group is generated by 3-cycles (3-element transpositions) or is structurally characterized as a 3-transposition group.
-
E.
hasSiblingExchange
Indicates a reciprocal relationship in which two entities are siblings of each other.
- F. None of above. chosen
Provenance (4 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: April 28, 2026, 1:26 p.m.