Triple
T3596115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Quintín Glacier |
E76143
|
entity |
| Predicate | hasRetreatTrend |
P5318
|
FINISHED |
| Object | retreating |
—
|
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: retreating | Statement: [San Quintín Glacier, hasRetreatTrend, retreating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetreatTrend Context triple: [San Quintín Glacier, hasRetreatTrend, retreating]
-
A.
hasRetreatedSince
Indicates that an entity has withdrawn or moved back from a position or engagement at some point after a specified reference time or event.
-
B.
isRetreating
Indicates that an entity is moving away from a location, opponent, or situation, typically to withdraw or escape from engagement.
-
C.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
D.
hasTendency
Indicates that an entity is inclined or likely to exhibit a particular behavior, characteristic, or outcome under certain conditions.
-
E.
retrocededTo
Indicates that control, ownership, or rights over something were returned or transferred back from one entity to another.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc19b26bc8190b3cc0613a1a98361 |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.