Triple
T24894485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Govone |
E623097
|
entity |
| Predicate | castleInstanceOf |
P106681
|
FINISHED |
| Object | historic residence |
—
|
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: historic residence | Statement: [Govone, castleInstanceOf, historic residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castleInstanceOf Context triple: [Govone, castleInstanceOf, historic residence]
-
A.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
B.
castleFunction
chosen
Indicates the primary role, purpose, or use that a castle serves (e.g., defense, residence, administration, or symbolism).
-
C.
castleBuiltOf
Indicates that a castle is constructed primarily from a specified material.
-
D.
castleRepresents
Indicates that a castle stands as a symbol or representation of another entity, concept, or value.
-
E.
castleBuiltFor
Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:26 a.m.