Triple
T38678055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomebamba |
E943810
|
entity |
| Predicate | partlyOverbuiltBy |
P49927
|
FINISHED |
| Object | Spanish colonial city of Cuenca |
—
|
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: Spanish colonial city of Cuenca | Statement: [Tomebamba, partlyOverbuiltBy, Spanish colonial city of Cuenca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlyOverbuiltBy Context triple: [Tomebamba, partlyOverbuiltBy, Spanish colonial city of Cuenca]
-
A.
partlyBuiltOverBy
chosen
Indicates that one entity is constructed so that it covers or overlaps only a portion of another entity’s area or structure.
-
B.
partlyRebuilt
Indicates that an entity has been reconstructed or restored to some extent, but not fully.
-
C.
builtUpBy
Indicates that something has been constructed, developed, or formed through the actions or contributions of a specified agent or process.
-
D.
laterBuiltOverBy
Indicates that a structure or feature was constructed at a later time on top of, or replacing, an earlier one.
-
E.
builtAsPartOf
Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.