Triple
T19320012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. President |
E483196
|
entity |
| Predicate | hasFormalityRequirement |
P83073
|
FINISHED |
| Object | used in official proceedings |
—
|
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: used in official proceedings | Statement: [Mr. President, hasFormalityRequirement, used in official proceedings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormalityRequirement Context triple: [Mr. President, hasFormalityRequirement, used in official proceedings]
-
A.
hasObligationForm
Indicates that one entity is required to use or comply with a specific formal document, format, or procedure as part of an obligation.
-
B.
hasFormalStatus
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
C.
hasFormalConstraint
Indicates that an entity is governed or restricted by an explicitly defined formal rule, condition, or limitation.
-
D.
admissionRequired
Indicates that access to something is conditional on being formally admitted or granted entry beforehand.
-
E.
formatRequirement
chosen
Indicates that one entity specifies the required structure, style, or arrangement that another entity must follow or conform to.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d87a0088190a60201b1f388089e |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.