Triple
T28502932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naso |
E721284
|
entity |
| Predicate | notableBearerCulture |
P203117
|
FINISHED |
| Object | Roman |
—
|
LITERAL FINISHED |
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: Roman | Statement: [Naso, notableBearerCulture, Roman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerCulture Context triple: [Naso, notableBearerCulture, Roman]
-
A.
notableBearerEthnicity
Indicates that the notable person bearing something (such as a name, title, or role) belongs to a specified ethnic group.
-
B.
notableBearerNationality
Indicates that the subject has a notable bearer whose nationality is the specified object.
-
C.
standardBearerCulture
Indicates that an entity serves as the primary or emblematic representative of a particular culture.
-
D.
notableBearerVariantOf
Indicates that one entity is a notable or prominent variant or version of another entity that bears or carries its characteristics.
-
E.
notableBearerDescription
Indicates that the subject has a notable bearer, with the object providing a textual description of that bearer’s significance or identity.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a0124a5d7848190a6b56d18db2f661d |
completed | May 11, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_6a01243da1808190ada3ce553e3f55b6 |
completed | May 11, 2026, 12:35 a.m. |
| PDg | Predicate description generation | batch_6a0124a538a08190b42e6f35d216da74 |
completed | May 11, 2026, 12:36 a.m. |
Created at: April 28, 2026, 3:07 a.m.