Triple
T23644083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julia Agricola |
E583980
|
entity |
| Predicate | praenomenOrNomen |
P153012
|
FINISHED |
| Object | Julia |
—
|
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: Julia | Statement: [Julia Agricola, praenomenOrNomen, Julia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: praenomenOrNomen Context triple: [Julia Agricola, praenomenOrNomen, Julia]
-
A.
praenomenTransliteration
Indicates the transliterated form of a person's Latin praenomen (given name) from its original script into a standardized Latin-letter representation.
-
B.
praenomenCommonlyUsed
Indicates that a particular praenomen (personal first name) is commonly used or frequently occurring within a given context or population.
-
C.
isPraenomenOf
Indicates that a given personal name functions as the praenomen (given name) of a specific individual.
-
D.
praenomenPosition
Indicates the relative ordering or placement of a person's praenomen (given name) within a full name or sequence of names.
-
E.
praenomenStatus
Indicates the status or role associated with a person's praenomen (given name), such as whether it is official, alternative, uncertain, or otherwise qualified.
- F. None of above. chosen
Provenance (4 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2832d9c8190b19c55deee39eff2 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:48 p.m.