Triple

T13444177
Position Surface form Disambiguated ID Type / Status
Subject Per Martin-Löf E320437 entity
Predicate givenName P17 FINISHED
Object Per E104102 NE 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: Per | Statement: [Per Martin-Löf, givenName, Per]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Per
Context triple: [Per Martin-Löf, givenName, Per]
  • A. Per chosen
    Per is a Scandinavian masculine given name, commonly used in Norway, Sweden, and Denmark as a form of Peter.
  • B. Pe
    Pe is a Hebrew consonant letter that represents a "p" or "f" sound and has both standard and final written forms.
  • C. PER
    PER is the IATA airport code for Perth Airport, the main international and domestic gateway serving Perth in Western Australia.
  • D. PER
    PER is the FIFA country code used to represent the Peru national football team in international competitions and official records.
  • E. PER
    PER is the stock ticker symbol under which Perot Systems, an information technology services company founded by Ross Perot, was traded on public markets.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaee881888190811ddf01bc699864 completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f739965ef081909e85881ce805bbb5 completed May 3, 2026, 12:03 p.m.
Created at: April 9, 2026, 9:40 p.m.