Triple
T37630819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Città Pinto |
E936336
|
entity |
| Predicate | appliedAsTitleTo |
P173685
|
FINISHED |
| Object | town of Qormi |
—
|
NE NERFINISHED |
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: town of Qormi | Statement: [Città Pinto, appliedAsTitleTo, town of Qormi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedAsTitleTo Context triple: [Città Pinto, appliedAsTitleTo, town of Qormi]
-
A.
appliedToTitle
Indicates that something (such as a rule, action, or attribute) is applied specifically to a given title.
-
B.
appliedToTitleHolder
Indicates that an action, rule, or condition is directed specifically toward the current holder of a particular title or position.
-
C.
usedAsTitleFrom
Indicates that something functions as a title derived from or originating from another source or context.
-
D.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
E.
usedAsTitleOn
chosen
Indicates that something functions as a title applied to or displayed on a particular entity.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:18 p.m.