Triple
T29572228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman engineering |
E753343
|
entity |
| Predicate | usedPrimaryLanguage |
P83252
|
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: [Roman engineering, usedPrimaryLanguage, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPrimaryLanguage Context triple: [Roman engineering, usedPrimaryLanguage, Latin]
-
A.
hasPrimaryLanguage1
chosen
Indicates that an entity’s main or most commonly used language is the specified language.
-
B.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
C.
primaryLanguageIn
Indicates that a specified language is the main or official language used within a particular place, organization, or context.
-
D.
primaryLanguageType
Indicates the main category or kind of language (such as spoken, written, or signed) that serves as the primary mode of communication in a given context or for a given entity.
-
E.
primaryVocalLanguage
Indicates the main spoken language typically used by an entity for vocal communication.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 5:59 p.m.