Triple

T29782783
Position Surface form Disambiguated ID Type / Status
Subject Turdus lherminieri E756167 entity
Predicate primaryStratumUsed P165800 FINISHED
Object understory and midstory 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: understory and midstory | Statement: [Turdus lherminieri, primaryStratumUsed, understory and midstory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryStratumUsed
Context triple: [Turdus lherminieri, primaryStratumUsed, understory and midstory]
  • A. primaryStratum chosen
    Indicates that one stratum is the main or most significant layer or level in relation to other associated strata.
  • B. preferredStrata
    Indicates the geological or social layers that an entity most favors, prioritizes, or tends to occupy or interact with over others.
  • C. primaryTerminalFor
    Indicates that one entity serves as the main or principal terminal associated with another entity.
  • D. primaryInterchange
    Indicates that one entity serves as the main point of exchange, transfer, or connection between systems, routes, or components relative to another entity.
  • E. hasStratum
    Indicates that one entity possesses, contains, or is associated with a particular layer or stratum within its structure or organization.
  • 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_69f22451fb748190bbdbab401280affb completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_6a019037edbc8190bdaec436ac2fcec6 completed May 11, 2026, 8:15 a.m.
PD Predicate disambiguation batch_6a018fe05a34819080068f588b5ff80c completed May 11, 2026, 8:14 a.m.
Created at: April 29, 2026, 5:06 p.m.