Triple
T15816873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gross Domestic Product |
E383502
|
entity |
| Predicate | timeDimension |
P67393
|
FINISHED |
| Object | quarterly |
—
|
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: quarterly | Statement: [Gross Domestic Product, timeDimension, quarterly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDimension Context triple: [Gross Domestic Product, timeDimension, quarterly]
-
A.
hasTimeDimension
chosen
Indicates that something possesses or is associated with a temporal aspect, such as duration, point in time, or time-based variation.
-
B.
dimensionOfTime
Indicates a temporal measurement or extent that specifies how long something lasts or when it occurs.
-
C.
timeCharacteristic
Indicates a relationship where one entity specifies a temporal property, feature, or constraint that characterizes another entity or event.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timeDomain
Indicates that something is characterized, defined, or analyzed with respect to time rather than another domain (such as frequency or space).
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a306a48190840adc49df2c26c5 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.