Triple
T9627546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore 1965 paper |
E232506
|
entity |
| Predicate | laterRevisedTo |
P35338
|
FINISHED |
| Object | doubling of components approximately every two years |
—
|
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: doubling of components approximately every two years | Statement: [Moore 1965 paper, laterRevisedTo, doubling of components approximately every two years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRevisedTo Context triple: [Moore 1965 paper, laterRevisedTo, doubling of components approximately every two years]
-
A.
dateRevisedTo
Indicates that an entity’s date has been updated or changed to a new specified date.
-
B.
revisionOf
chosen
Indicates that one entity is a modified or updated version of another earlier entity.
-
C.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
D.
laterRepublishedWith
Indicates that an existing work was republished at a later time in a modified or updated form specified by the related entity.
-
E.
revisedAfterCouncil
Indicates that one entity was revised or modified following the conclusion or decisions of a council.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afeb64c8190be91024c2e9039d3 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.