Triple
T331729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Revised Standard Version |
E6638
|
entity |
| Predicate | scholarlyReputation |
P5129
|
FINISHED |
| Object | high |
—
|
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 | Statement: [New Revised Standard Version, scholarlyReputation, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scholarlyReputation Context triple: [New Revised Standard Version, scholarlyReputation, high]
-
A.
academicReputation
chosen
Indicates the perceived quality and standing of an entity within the academic community, based on factors like scholarly impact, prestige, and recognition.
-
B.
researchStrength
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
-
C.
scholarlyView
Indicates that one entity holds an academic or research-based interpretation, opinion, or theoretical stance about another entity.
-
D.
scholarlyUse
Indicates that something is used for academic, educational, or research-related purposes.
-
E.
hasAcademicAffiliation
Indicates that an entity is formally associated with an academic institution, such as through employment, enrollment, or official collaboration.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eab1a7048190ac690ddc2e294914 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.