Triple
T2200283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annuit cœptis |
E50471
|
entity |
| Predicate | tense |
P9327
|
FINISHED |
| Object | perfect |
—
|
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: perfect | Statement: [Annuit cœptis, tense, perfect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tense Context triple: [Annuit cœptis, tense, perfect]
-
A.
hasTense
chosen
Indicates that an action, event, or state is associated with a specific grammatical tense (such as past, present, or future).
-
B.
hasTenseAspect
Indicates that a verb or clause is associated with a specific grammatical tense and aspect configuration.
-
C.
tension
Indicates a state of strain, stress, or conflict existing between entities, often involving opposing forces, interests, or emotions.
-
D.
hasTenseAspectSystem
Indicates that a language or clause employs a particular system for expressing tense and aspect distinctions.
-
E.
grammaticalMood
Indicates the grammatical mood used in an utterance, specifying the speaker’s attitude toward the action or state (such as indicative, imperative, or subjunctive).
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa06bb4819092d7021358846e5f |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.