Triple
T31592277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio XVII |
E806129
|
entity |
| Predicate | standardBearerCulture |
P181770
|
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: [Legio XVII, standardBearerCulture, Roman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardBearerCulture Context triple: [Legio XVII, standardBearerCulture, Roman]
-
A.
defaultCulture
Indicates that one culture is designated as the primary or standard culture used by default in a given context or system.
-
B.
isCulturalStandardFor
Indicates that something is recognized or accepted as the customary or normative practice, value, or behavior within a particular culture or cultural context.
-
C.
supportsCulture
Indicates that one entity actively promotes, sustains, or enhances the cultural practices, values, or expressions associated with another entity.
-
D.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
E.
usesCulture
Indicates that one entity employs, incorporates, or relies on the cultural practices, norms, or artifacts associated with another entity in its actions or functioning.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 30, 2026, 10:28 p.m.