Triple
T14227921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nec aspera terrent |
E352670
|
entity |
| Predicate | subjectImplied |
P36922
|
FINISHED |
| Object | we |
—
|
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: we | Statement: [Nec aspera terrent, subjectImplied, we]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectImplied Context triple: [Nec aspera terrent, subjectImplied, we]
-
A.
subjectImpliedAs
chosen
Indicates that the subject of an action or statement is not explicitly stated but is understood or inferred from context.
-
B.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
C.
subjectKey
Indicates that the subject serves as a unique key or identifier used to reference or distinguish an entity in a relationship or dataset.
-
D.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
E.
subjectMVP
Indicates that the subject is considered the most valuable player (MVP) in a given context or event.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622a48508190bbfedb762bd1674d |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.