Triple
T20404340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Rough and Ready |
E500424
|
entity |
| Predicate | hasShortLivedExistence |
P3981
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Republic of Rough and Ready, hasShortLivedExistence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShortLivedExistence Context triple: [Republic of Rough and Ready, hasShortLivedExistence, true]
-
A.
isShortLived
chosen
Indicates that an entity exists or remains in a particular state for only a brief or limited period of time.
-
B.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
C.
hasNoLongerExistsAs
Indicates that an entity previously existed in a certain form, state, or identity but no longer exists in that form.
-
D.
hasLifetimeStatus
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
-
E.
hasExistenceStatus
Indicates that an entity is associated with a particular state of existence, such as being current, historical, planned, or no longer existing.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6799161c48190825eca3027d1aa51 |
completed | April 20, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.