Triple
T30843957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephanus’s Greek New Testament |
E785585
|
entity |
| Predicate | editorFrenchName |
P6538
|
FINISHED |
| Object | Robert Étienne |
—
|
NE NERFINISHED |
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: Robert Étienne | Statement: [Stephanus’s Greek New Testament, editorFrenchName, Robert Étienne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorFrenchName Context triple: [Stephanus’s Greek New Testament, editorFrenchName, Robert Étienne]
-
A.
nameInFrench
chosen
Indicates that an entity is known or referred to by a specific name expressed in the French language.
-
B.
isFrancophoneCounterpartOf
Indicates that one entity serves as the French-speaking or French-language equivalent or counterpart of another entity.
-
C.
FrenchForm
Indicates that one entity is a form, version, or expression of another specifically in the French language.
-
D.
FrenchComponent
Indicates that something is a component, part, or element that is specifically French in origin, language, or context.
-
E.
equivalentFrenchPostNominal
Indicates that one entity has a corresponding or matching French post-nominal form equivalent to that of another entity.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:46 p.m.