Triple

T4214809
Position Surface form Disambiguated ID Type / Status
Subject Hayabusa E94188 entity
Predicate sampleCollectionMethod P9384 FINISHED
Object projectile impact and capture in collection horn 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: projectile impact and capture in collection horn | Statement: [Hayabusa, sampleCollectionMethod, projectile impact and capture in collection horn]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sampleCollectionMethod
Context triple: [Hayabusa, sampleCollectionMethod, projectile impact and capture in collection horn]
  • A. currentCollectionMethod
    Indicates the method or process currently being used to collect something (such as data, payments, or materials) from an entity.
  • B. collectedThrough chosen
    Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
  • C. surveyMethod
    Indicates the technique or procedure used to conduct a survey or collect survey data.
  • D. powerCollectionMethod
    Indicates the method or process by which power is collected, harvested, or obtained in a given context.
  • E. dataTypeCollected
    Indicates that a specific type or category of data is gathered or recorded in the context of an entity 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_69b3451997e08190851db4a9a588837d completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b34e098da881909a0cc339cc186627 completed March 12, 2026, 11:36 p.m.
PD Predicate disambiguation batch_69b347efd9b08190bb50f82e4e7fe06d completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:04 p.m.