Triple
T30221125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | censor (Roman Republic) |
E768346
|
entity |
| Predicate | maximumIntervalBetweenCensuses |
P181067
|
FINISHED |
| Object | 5 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: 5 years | Statement: [censor (Roman Republic), maximumIntervalBetweenCensuses, 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumIntervalBetweenCensuses Context triple: [censor (Roman Republic), maximumIntervalBetweenCensuses, 5 years]
-
A.
timeBetweenCensusAndUse
Indicates the length of time that passes between when a census is conducted and when its data is used for a particular purpose.
-
B.
occursBetweenCensuses
Indicates that an event or state takes place in the time interval between two consecutive census dates.
-
C.
nextScheduledCensusYear
Indicates the year in which the next planned or officially scheduled census is to take place.
-
D.
latestInterval
Indicates that the related interval is the most recent or last occurring time span among a set of intervals.
-
E.
apportionmentInterval
Indicates the time span or interval over which something (such as a quantity, cost, or resource) is allocated or distributed.
- F. None of above. chosen
Provenance (4 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 29, 2026, 7:35 p.m.