Triple
T607065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clouds |
E12016
|
entity |
| Predicate | hasRevisedVersion |
P12710
|
FINISHED |
| Object | second edition by Aristophanes |
—
|
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: second edition by Aristophanes | Statement: [Clouds, hasRevisedVersion, second edition by Aristophanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevisedVersion Context triple: [Clouds, hasRevisedVersion, second edition by Aristophanes]
-
A.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
B.
revisionKnownAs
chosen
Indicates that a particular revision of an entity is referred to or identified by a specific alternative name or label.
-
C.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
D.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
E.
isUpdatedThrough
Indicates that one entity’s state or content is modified or brought up to date as a result of a process, action, or interaction involving another entity.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df34abc8190a578c8c2ab3d28e4 |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cf8fc1c81908a9c7df552aa1a59 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.