Triple

T10463985
Position Surface form Disambiguated ID Type / Status
Subject Japanese South Pacific Mandate E246743 entity
Predicate mandateClass P94176 FINISHED
Object Class C 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: Class C | Statement: [Japanese South Pacific Mandate, mandateClass, Class C]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mandateClass
Context triple: [Japanese South Pacific Mandate, mandateClass, Class C]
  • A. mandateDefinedBy
    Indicates that the scope, authority, or responsibilities of one entity’s mandate are formally established or specified by another entity or source.
  • B. mandateFrom
    Indicates that one entity has been granted authoritative permission or instruction by another entity to act or decide on its behalf.
  • C. mandateForNP
    Indicates that an authority formally requires or authorizes a particular action, policy, or responsibility to be carried out by or for the referenced noun phrase.
  • D. mandateLevel
    Indicates the degree or strictness of obligation imposed by a rule, policy, or authority on an action or relationship.
  • E. mandateRestriction
    Indicates that an authority imposes a binding limitation or requirement on an entity’s actions or conditions.
  • F. None of above. chosen

Provenance (4 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_69d381c16c248190a2fe5b471e584e9c completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d50885e220819089e455b646f31e65 completed April 7, 2026, 1:37 p.m.
PD Predicate disambiguation batch_69d4fb7d353c8190a73f439a956c7606 completed April 7, 2026, 12:41 p.m.
PDg Predicate description generation batch_69d4fe058fcc81909428137d9ffd6d90 completed April 7, 2026, 12:52 p.m.
Created at: April 6, 2026, 12:19 p.m.