Triple
T28349223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James (given name) |
E718042
|
entity |
| Predicate | hasFormInLateLatin |
P137467
|
FINISHED |
| Object | Iacobus |
—
|
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: Iacobus | Statement: [James (given name), hasFormInLateLatin, Iacobus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormInLateLatin Context triple: [James (given name), hasFormInLateLatin, Iacobus]
-
A.
hasLatinInfluence
Indicates that one entity exerts or reflects cultural, linguistic, or stylistic influence derived from Latin on another entity.
-
B.
hasLaterFormLanguage
chosen
Indicates that one language has a subsequent or later-developed form or variant in another language.
-
C.
hasLatinAdjectiveForm
Indicates that an entity has a corresponding adjectival form in Latin derived from its name or designation.
-
D.
hasLanguageFormOf
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
-
E.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 12:45 a.m.