Triple
T17481394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caspian tiger |
E425667
|
entity |
| Predicate | historicalRangeType |
P127623
|
FINISHED |
| Object | continental interior |
—
|
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: continental interior | Statement: [Caspian tiger, historicalRangeType, continental interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRangeType Context triple: [Caspian tiger, historicalRangeType, continental interior]
-
A.
historicalRange
Indicates the time period over which something existed, was active, or was relevant in history.
-
B.
historicalValue
Indicates that something possesses significance, importance, or relevance due to its connection with past events, periods, or developments.
-
C.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
D.
historicalPartitionPeriod
Indicates that an entity existed, occurred, or is relevant during a specific historical period of territorial partition.
-
E.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bfd75481908c20bc2c1cbff593 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:48 a.m.