Triple

T31886135
Position Surface form Disambiguated ID Type / Status
Subject AL 288-1 E814011 entity
Predicate importanceInField P54903 FINISHED
Object key evidence for early hominin bipedalism 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: key evidence for early hominin bipedalism | Statement: [AL 288-1, importanceInField, key evidence for early hominin bipedalism]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: importanceInField
Context triple: [AL 288-1, importanceInField, key evidence for early hominin bipedalism]
  • A. importanceInEvent
    Indicates the degree to which an entity plays a significant or central role within a particular event.
  • B. resultImportance
    Indicates that one entity specifies how significant, critical, or impactful the outcome or result of another entity is.
  • C. peakImportance
    Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
  • D. fieldOfSignificance chosen
    Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
  • E. importanceInLap
    Indicates the degree to which something is significant or influential within a specific lap or iteration of an event or process.
  • 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_69f348ef817481908440e2250319bcc8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f707f7959881908f037f0d6b1d0c36 completed May 3, 2026, 8:31 a.m.
PD Predicate disambiguation batch_69f700fc274c8190a128593dc7c7abd0 completed May 3, 2026, 8:02 a.m.
Created at: April 30, 2026, 11:57 p.m.