Triple

T32318830
Position Surface form Disambiguated ID Type / Status
Subject ICAO Chapter 4 E825714 entity
Predicate hasStricterLimitsThan P90714 FINISHED
Object ICAO Chapter 3 NE NERFINISHED

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: ICAO Chapter 3 | Statement: [ICAO Chapter 4, hasStricterLimitsThan, ICAO Chapter 3]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStricterLimitsThan
Context triple: [ICAO Chapter 4, hasStricterLimitsThan, ICAO Chapter 3]
  • A. hasMoreRestrictionsThan
    Indicates that one entity is subject to a greater number or stricter set of limitations, rules, or constraints than another entity.
  • B. hasStricterStandardThan chosen
    Indicates that one entity’s rules, criteria, or requirements are more demanding or rigorous than those of another entity.
  • C. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • D. hasLimitation
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • E. hasMoreLimitedJurisdictionThan
    Indicates that one authority or entity’s legal power or scope of control is narrower or more restricted than that of another.
  • 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_69f34912d0c48190bba75770660320e9 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ff0b6bc4a88190bf1d38c6ea26bcdc completed May 9, 2026, 10:24 a.m.
PD Predicate disambiguation batch_69ff082a22f4819095ded971dbd8ea7b completed May 9, 2026, 10:10 a.m.
Created at: May 1, 2026, 12:46 a.m.