Triple
T5364252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Alliance (1882) |
E103091
|
entity |
| Predicate | renewalFrequency |
P5690
|
FINISHED |
| Object | every five years |
—
|
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: every five years | Statement: [Triple Alliance (1882), renewalFrequency, every five years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renewalFrequency Context triple: [Triple Alliance (1882), renewalFrequency, every five years]
-
A.
renewalTerm
Indicates the length or conditions of time for which an agreement, contract, or subscription is extended beyond its initial term.
-
B.
renewalMethod
Indicates the method or process by which something (such as a contract, subscription, or agreement) is renewed.
-
C.
renewalPattern
chosen
Indicates the recurring schedule or frequency with which something is renewed or repeated over time.
-
D.
renewalGracePeriod
Indicates the time window after a subscription or contract expires during which it can still be renewed without being treated as fully lapsed or terminated.
-
E.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865d42508190a1a96121674c1020 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.