Triple
T34769084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Session |
E1002306
|
entity |
| Predicate | basedOnPerformanceDate |
P198866
|
FINISHED |
| Object | December 1983 |
—
|
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: December 1983 | Statement: [In Session, basedOnPerformanceDate, December 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPerformanceDate Context triple: [In Session, basedOnPerformanceDate, December 1983]
-
A.
basedOnPerformanceBy
Indicates that something is derived from, adapted from, or determined according to the performance carried out by a particular entity.
-
B.
lastPerformanceDate
Indicates the date on which an entity most recently carried out a performance or event.
-
C.
balanceOfPerformance
Indicates a relationship where performance characteristics between entities are adjusted or equalized to maintain fairness or parity.
-
D.
performanceBasis
Indicates that one entity’s performance is evaluated, determined, or justified on the basis of another specified factor, standard, or reference.
-
E.
basedOnMaterialPeriod
Indicates that something is determined, classified, or characterized according to the material period from which it originates or to which it belongs.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
| PDg | Predicate description generation | batch_69ff0e9b7acc81909a0ee66201a06877 |
completed | May 9, 2026, 10:38 a.m. |
Created at: May 3, 2026, 3:59 p.m.