Triple
T33286888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Thaw |
E852202
|
entity |
| Predicate | hasPrehistoricParasite |
P203443
|
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: [The Thaw, hasPrehistoricParasite, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrehistoricParasite Context triple: [The Thaw, hasPrehistoricParasite, yes]
-
A.
hasFossilEvidence
Indicates that there exists fossil-based evidence supporting the existence, occurrence, or characteristics of the related entity or event.
-
B.
historicPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
-
C.
knownSincePrehistoricTimes
Indicates that the relationship or fact has been recognized or established by humans since prehistoric times, long before written history.
-
D.
parasitizes
Indicates a relationship in which one organism lives on or in another organism, deriving nutrients or benefits at the host’s expense.
-
E.
isInfestedWith
Indicates that one entity is overrun, occupied, or contaminated by another, typically unwanted, organism or agent.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a017e7bdfe481909cb4d5bdede6035e |
completed | May 11, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_6a017defee108190bdf5f98dc415b250 |
completed | May 11, 2026, 6:57 a.m. |
| PDg | Predicate description generation | batch_6a017e7b0ef4819090f82220b73d0888 |
completed | May 11, 2026, 7 a.m. |
Created at: May 1, 2026, 1:32 a.m.