Triple
T21913909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ut queant laxis |
E541131
|
entity |
| Predicate | laterDevelopmentFrom |
P1245
|
FINISHED |
| Object | Gregorian hymn 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: Gregorian hymn tradition | Statement: [Ut queant laxis, laterDevelopmentFrom, Gregorian hymn tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDevelopmentFrom Context triple: [Ut queant laxis, laterDevelopmentFrom, Gregorian hymn tradition]
-
A.
laterDevelopments
Indicates that subsequent events, changes, or outcomes occurred following an earlier situation or state.
-
B.
developedFrom
chosen
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
C.
developedThrough
Indicates that something came into existence, was created, or was brought to its current form by means of a specified process, method, or developmental pathway.
-
D.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
E.
developsDuring
Indicates that one process, condition, or characteristic comes into existence or forms over the course of a specified time period, phase, or event.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123359e1c8190a606a92c5bcb58e8 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:42 p.m.