Triple
T29902335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Calendarist movement |
E759442
|
entity |
| Predicate | internalCharacteristic |
P128001
|
FINISHED |
| Object | high degree of fragmentation |
—
|
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: high degree of fragmentation | Statement: [Old Calendarist movement, internalCharacteristic, high degree of fragmentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalCharacteristic Context triple: [Old Calendarist movement, internalCharacteristic, high degree of fragmentation]
-
A.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
B.
sharedCharacteristic
Indicates that two or more entities possess the same specified attribute or quality.
-
C.
entityCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
D.
ribCharacteristic
Indicates that a specified characteristic or property is associated with a rib.
-
E.
codeCharacteristic
Indicates that one piece of code possesses a specific property, feature, or quality in relation to another referenced aspect.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 6:07 p.m.