Triple

T24626188
Position Surface form Disambiguated ID Type / Status
Subject 1871 United States expedition to Korea E609546 entity
Predicate capturedItems P14511 FINISHED
Object Korean flags 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: Korean flags | Statement: [1871 United States expedition to Korea, capturedItems, Korean flags]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: capturedItems
Context triple: [1871 United States expedition to Korea, capturedItems, Korean flags]
  • A. capturedEquipment chosen
    Indicates that one party has taken possession of another party’s equipment, typically as a result of conflict, competition, or enforcement.
  • B. capturedFor
    Indicates that one entity has been taken into custody, control, or possession specifically for the benefit, use, or purpose of another entity.
  • C. capturedIn
    Indicates that one entity was taken prisoner, seized, or otherwise brought under control within the context, location, or event represented by another entity.
  • D. capturedUsing
    Indicates that something was recorded, obtained, or documented by means of a specified tool, method, or device.
  • E. possessedItem
    Indicates that one entity owns, holds, or has control over another entity as a possession.
  • 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_69e2c4d1d3708190a0f2dc6a3a8523bb completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f2be044d4c819094e14eda28d371a7 completed April 30, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69f2a6d0ab708190b2e3b94dd20ca76b completed April 30, 2026, 12:48 a.m.
Created at: April 18, 2026, 2:32 a.m.