Triple
T32908011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Junta of the Principality of Asturias |
E841793
|
entity |
| Predicate | hasTermLengthYears |
P33746
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [General Junta of the Principality of Asturias, hasTermLengthYears, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTermLengthYears Context triple: [General Junta of the Principality of Asturias, hasTermLengthYears, 4]
-
A.
termLength
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
B.
termLengthNumber
chosen
Indicates the numerical value representing the duration or length of a specified term.
-
C.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
-
D.
termLengthCondition
Indicates a condition or constraint specifying the required or allowed duration/length of a term (such as a contract, agreement, or period).
-
E.
termLengthCharacteristic
Indicates the specific duration-related property or feature associated with a term (such as its length or time span).
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 1:19 a.m.