Triple
T32392198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUA:IND |
E827700
|
entity |
| Predicate | isReconstituted |
P174462
|
FINISHED |
| Object | annually |
—
|
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: annually | Statement: [RUA:IND, isReconstituted, annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReconstituted Context triple: [RUA:IND, isReconstituted, annually]
-
A.
canBeReconstituted
Indicates that something has the capacity to be restored or returned to a prior or functional state, typically after being separated, dissolved, or broken down.
-
B.
reconstitutedFor
Indicates that something has been restored, rebuilt, or reassembled specifically for a particular purpose, use, or context.
-
C.
canReconstitute
Indicates that an entity has the ability to restore or reassemble another entity (or itself) back into a prior or whole state.
-
D.
reconstitutedFrom
Indicates that something has been restored, rebuilt, or reassembled using material, components, or information derived from another source.
-
E.
wasReconstructed
Indicates that something previously existing was rebuilt or restored after damage, destruction, or alteration.
- F. None of above. chosen
Provenance (4 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:52 a.m.