Triple
T3720587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meton of Athens |
E81627
|
entity |
| Predicate | calendarTypeWorkedOn |
P5453
|
FINISHED |
| Object | lunisolar calendar |
—
|
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: lunisolar calendar | Statement: [Meton of Athens, calendarTypeWorkedOn, lunisolar calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarTypeWorkedOn Context triple: [Meton of Athens, calendarTypeWorkedOn, lunisolar calendar]
-
A.
workChronicles
Indicates that one entity documents, records, or narrates the work-related activities, history, or experiences of another entity.
-
B.
calendarType
chosen
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
C.
coordinatesWorkOf
Indicates overseeing and organizing the tasks, efforts, or activities of others to ensure they work together effectively toward a common goal.
-
D.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
-
E.
calendarDependence
Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9b5ca8819094299fffc02606ce |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.