Triple
T7253144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnetic South Pole |
E157652
|
entity |
| Predicate | isTimeDependent |
P44297
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Magnetic South Pole, isTimeDependent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTimeDependent Context triple: [Magnetic South Pole, isTimeDependent, true]
-
A.
timeDependence
chosen
Indicates that one entity’s state, value, or behavior is determined by or varies as a function of another entity over time.
-
B.
durationDependsOn
Indicates that the length of time of one event or state is determined or influenced by another event, condition, or factor.
-
C.
hasTimeDepth
Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
-
D.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
-
E.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9d41908190bb76c6a5b9d5b1a2 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.