Triple
T27870471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baishou dance |
E704476
|
entity |
| Predicate | temporalOrigin |
P38044
|
FINISHED |
| Object | centuries-old tradition |
—
|
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: centuries-old tradition | Statement: [Baishou dance, temporalOrigin, centuries-old tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalOrigin Context triple: [Baishou dance, temporalOrigin, centuries-old tradition]
-
A.
timePeriodOrigin
chosen
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
B.
temporal
Indicates a relationship that situates one event, state, or entity in time relative to another (e.g., before, after, or during).
-
C.
temporal scope
Indicates the time period or duration over which a particular relationship, condition, or fact holds true.
-
D.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
-
E.
temporalAspect
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6394b0938819085ae266cc71eb0e4 |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:24 p.m.