Triple

T31357998
Position Surface form Disambiguated ID Type / Status
Subject With Folded Hands… E799787 entity
Predicate hasMottoOrRule P176275 FINISHED
Object To serve and obey and guard men from harm 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: To serve and obey and guard men from harm | Statement: [With Folded Hands…, hasMottoOrRule, To serve and obey and guard men from harm]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMottoOrRule
Context triple: [With Folded Hands…, hasMottoOrRule, To serve and obey and guard men from harm]
  • A. hasMottoAuthority
    Indicates that an entity has the official power or right to establish, approve, or oversee the use of a motto for another entity.
  • B. hasMottoSymbol
    Indicates that an entity’s motto is represented or accompanied by a particular symbol.
  • C. hasMottoLikeFunction
    Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
  • D. hasMottoElement
    Indicates that something includes a specific phrase or component as part of its motto.
  • E. hasMottoOrAssociation chosen
    Indicates a relationship where an entity is linked to a motto, slogan, or associated phrase that represents or characterizes it.
  • 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_69f224e5e9bc8190a16339328897c4f8 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fdb45537288190b6791078d4a6899f completed May 8, 2026, 10 a.m.
PD Predicate disambiguation batch_69fdb39ad96481908376d7def9fafc13 completed May 8, 2026, 9:57 a.m.
Created at: April 29, 2026, 9:17 p.m.