Triple
T24610629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antónia |
E609102
|
entity |
| Predicate | ultimateOriginLanguage |
P86181
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [Antónia, ultimateOriginLanguage, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimateOriginLanguage Context triple: [Antónia, ultimateOriginLanguage, Latin]
-
A.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
B.
indirectOriginLanguage
chosen
Indicates that something originates from a particular language, not directly but through one or more intermediate languages or sources.
-
C.
originalTextLanguage
Indicates the language in which a text was originally written or created before any translation or adaptation.
-
D.
originalLanguageContext
Indicates the language in which something was first created or expressed, providing the original linguistic context for its content or meaning.
-
E.
claimedOriginOfLanguage
Indicates that an entity asserts or is asserted to be the source or birthplace of a particular language.
- 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.