Triple
T404890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Living Translation |
E9361
|
entity |
| Predicate | translationTeam |
P3756
|
FINISHED |
| Object | over 90 evangelical scholars |
—
|
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: over 90 evangelical scholars | Statement: [New Living Translation, translationTeam, over 90 evangelical scholars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translationTeam Context triple: [New Living Translation, translationTeam, over 90 evangelical scholars]
-
A.
translator
Indicates that one entity serves to convert or render content from one language or form into another for a second entity.
-
B.
translationMethod
Indicates the technique or process used to translate content from one language or form to another.
-
C.
team
chosen
Indicates that multiple entities are grouped together as a collaborative unit working toward shared goals or tasks.
-
D.
managedTeamFrom
Indicates that one entity led, directed, or supervised a team originating from or based in another specified entity.
-
E.
managedTeam
Indicates that one entity had responsibility for directing, supervising, and coordinating the work of another group or team.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca37fe881909802126952dfdd59 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.