Triple
T22010063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Leucio complex |
E543550
|
entity |
| Predicate | CodiceLeucianoFeatures |
P128001
|
FINISHED |
| Object | equality of citizens |
—
|
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: equality of citizens | Statement: [San Leucio complex, CodiceLeucianoFeatures, equality of citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CodiceLeucianoFeatures Context triple: [San Leucio complex, CodiceLeucianoFeatures, equality of citizens]
-
A.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
B.
iconicFeature
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
-
C.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
-
D.
coreAreaCharacteristic
Indicates that a characteristic or feature is specifically associated with the core area of something, rather than its peripheral or secondary parts.
-
E.
entityCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a4338c8190836074d21bfbaf78 |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:22 p.m.