Triple
T1284772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masorti movement |
E27409
|
entity |
| Predicate | approachToTextStudy |
P1717
|
FINISHED |
| Object | historical-critical method |
—
|
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: historical-critical method | Statement: [Masorti movement, approachToTextStudy, historical-critical method]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachToTextStudy Context triple: [Masorti movement, approachToTextStudy, historical-critical method]
-
A.
interpreterOfWriting
Indicates that one entity serves to interpret, translate, or explain the written content produced or used by another entity.
-
B.
textualStructure
Indicates how parts of a text are organized and related to each other within its overall structure.
-
C.
researchApproach
chosen
Indicates the methodological strategy or set of methods used to conduct and structure a research activity or investigation.
-
D.
studiesProcess
Indicates that an entity systematically examines, researches, or learns about a particular process.
-
E.
textualTransmission
Indicates the transfer or communication of information through written or printed text from one source to another.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b6dda48190a2e79084adea6ec1 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.