Triple
T31077468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curiosum Urbis Romae |
E792003
|
entity |
| Predicate | describesTypeOfFeature |
P5048
|
FINISHED |
| Object | temples |
—
|
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: temples | Statement: [Curiosum Urbis Romae, describesTypeOfFeature, temples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesTypeOfFeature Context triple: [Curiosum Urbis Romae, describesTypeOfFeature, temples]
-
A.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
B.
describesCharacteristicOf
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
-
C.
descriptorType
Indicates that one entity serves as a descriptive attribute or classification of another entity.
-
D.
featureTypeCatalog
Indicates that an entity is associated with, or defined by, a catalog that specifies the types of features it can include or reference.
-
E.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 9:02 p.m.