Triple

T18998467
Position Surface form Disambiguated ID Type / Status
Subject GAF (informal) E464882 entity
Predicate denotesServiceStatus P8487 FINISHED
Object wartime rank 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: wartime rank | Statement: [GAF (informal), denotesServiceStatus, wartime rank]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: denotesServiceStatus
Context triple: [GAF (informal), denotesServiceStatus, wartime rank]
  • A. typicalServiceStatus
    Indicates the usual or standard operational state or condition that a service is expected to be in under normal circumstances.
  • B. serviceEntryStatus
    Indicates the current state or condition of a service entry within a process or system (e.g., whether it is active, pending, completed, or otherwise classified).
  • C. serviceNumberStatus
    Indicates the current operational or availability state associated with a specific service number.
  • D. statusIndicates chosen
    Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
  • E. maintenanceStatus
    Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
  • 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_69d8dd01a56c81909694a128c66b21d7 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6838f4481909b265e29964b0dca completed April 20, 2026, 7:32 a.m.
PD Predicate disambiguation batch_69e4a2f88e0c81908cb20f08bf24cd32 completed April 19, 2026, 9:40 a.m.
Created at: April 10, 2026, 12:01 p.m.