Triple
T11787447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timiryazevskaya |
E280305
|
entity |
| Predicate | isOnNorthSouthAxis |
P70156
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Timiryazevskaya, isOnNorthSouthAxis, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnNorthSouthAxis Context triple: [Timiryazevskaya, isOnNorthSouthAxis, yes]
-
A.
isOnAxis
Indicates that one entity lies directly along a specified axis or reference line defined by another entity or coordinate system.
-
B.
northSouthAxis
chosen
Indicates a spatial or directional relationship aligned along the north–south axis between entities.
-
C.
isAxisBetween
Indicates that one entity serves as a central or reference axis positioned between two other entities in a spatial or structural arrangement.
-
D.
usesAxis
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
-
E.
isMajorAxisFor
Indicates that something serves as the primary or longest axis that defines the main directional or structural orientation of another object or system.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a586803481909af0032c35ca6e51 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.