Triple
T347060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvre Museum |
E6963
|
entity |
| Predicate | constructionBeganAsFortressIn |
P12643
|
FINISHED |
| Object | late 12th century |
—
|
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: late 12th century | Statement: [Louvre Museum, constructionBeganAsFortressIn, late 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionBeganAsFortressIn Context triple: [Louvre Museum, constructionBeganAsFortressIn, late 12th century]
-
A.
castleBuiltFor
Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
-
B.
historicalStronghold
Indicates that a location has historically served as a fortified center of power, defense, or control for a group or authority.
-
C.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
-
D.
castleLaterOwnedBy
Indicates that ownership of a castle passed to a specified entity at a later time than the initial or previously recorded owner.
-
E.
currentStronghold
Indicates that an entity currently serves as the primary base, fortress, or central stronghold for another entity.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1a37c08190b1380f6bf8513a37 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2eae0bd7081908197bbf5c55fe647 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.