Triple
T33048708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iglesia de San Juan de Baños |
E845666
|
entity |
| Predicate | hasApseCount |
P116215
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Iglesia de San Juan de Baños, hasApseCount, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApseCount Context triple: [Iglesia de San Juan de Baños, hasApseCount, 3]
-
A.
hasApse
Indicates that a structure or building possesses an apse, typically a semicircular or polygonal recess, as one of its architectural features.
-
B.
numberOfApses
chosen
Indicates the quantity of apses associated with a given structure or entity.
-
C.
areCountedBy
Indicates that one entity serves as the counting mechanism, record, or process by which the quantity of another entity is determined.
-
D.
hasBaseCount
Indicates the number of base units or fundamental components associated with an entity.
-
E.
hasPitchCount
Indicates that an entity is associated with a specific number of pitches, representing how many pitches have occurred or been recorded for it.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 1:24 a.m.