Triple
T16451837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teate Marrucinorum |
E399569
|
entity |
| Predicate | hasNameQualifierMeaning |
P24069
|
FINISHED |
| Object | of the Marrucini |
—
|
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: of the Marrucini | Statement: [Teate Marrucinorum, hasNameQualifierMeaning, of the Marrucini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameQualifierMeaning Context triple: [Teate Marrucinorum, hasNameQualifierMeaning, of the Marrucini]
-
A.
hasBaseNameMeaning
Indicates that an entity’s base name carries or is associated with a particular meaning.
-
B.
hasNameCharacteristic
Indicates that an entity possesses a specific quality or attribute related to its name.
-
C.
hasFinisherNameMeaning
Indicates that an entity’s finishing move is associated with a specific meaning or interpretation of its name.
-
D.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
E.
hasGivenNameMeaning
chosen
Indicates that a given name carries a particular meaning or semantic interpretation.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ce19344819083d323077b742bc3 |
completed | April 18, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.