Triple
T24621213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaestiones celeberrimae in Genesim |
E609416
|
entity |
| Predicate | discussesText |
P33880
|
FINISHED |
| Object | Genesis 1 |
—
|
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: Genesis 1 | Statement: [Quaestiones celeberrimae in Genesim, discussesText, Genesis 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discussesText Context triple: [Quaestiones celeberrimae in Genesim, discussesText, Genesis 1]
-
A.
discussed
Indicates that one entity talked about, examined, or debated a topic, issue, or other entity with someone else.
-
B.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
C.
discussionsTo
Indicates a relationship in which one entity leads to, results in, or gives rise to discussions involving another entity.
-
D.
containsDiscussionOf
chosen
Indicates that one entity includes or features a discussion, treatment, or consideration of another entity as a topic or subject.
-
E.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.