Triple
T20221562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrés de Fonollosa |
E495265
|
entity |
| Predicate | usesAliasConvention |
P139276
|
FINISHED |
| Object | city name code-names |
—
|
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: city name code-names | Statement: [Andrés de Fonollosa, usesAliasConvention, city name code-names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAliasConvention Context triple: [Andrés de Fonollosa, usesAliasConvention, city name code-names]
-
A.
usesAliasFor
Indicates that one entity employs an alternative name or identifier to refer to another entity.
-
B.
usesAliasTo
Indicates that one entity employs an alternative name or identifier to refer to or represent another entity.
-
C.
usedByAlias
Indicates that something is utilized, referenced, or accessed through an alternative name or alias.
-
D.
includesByConvention
Indicates that one entity is understood to include another as part of an accepted rule, norm, or customary practice rather than by explicit specification.
-
E.
isAliasOf
Indicates that one name, label, or identifier refers to the same entity as another.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd610f881908fdd22b1f8bd2efc |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:39 p.m.