Triple
T390542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tropic of Capricorn |
E8869
|
entity |
| Predicate | isReferenceFor |
P5454
|
FINISHED |
| Object | solar geometry calculations |
—
|
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: solar geometry calculations | Statement: [Tropic of Capricorn, isReferenceFor, solar geometry calculations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReferenceFor Context triple: [Tropic of Capricorn, isReferenceFor, solar geometry calculations]
-
A.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
B.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
C.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
D.
hasCanonicalReference
chosen
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
E.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5d73e881909101308a583c8f13 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.