Triple
T16174508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cité de Carcassonne |
E392526
|
entity |
| Predicate | developedAsFortressInCentury |
P77350
|
FINISHED |
| Object | 3rd 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: 3rd century | Statement: [Cité de Carcassonne, developedAsFortressInCentury, 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedAsFortressInCentury Context triple: [Cité de Carcassonne, developedAsFortressInCentury, 3rd century]
-
A.
fortressOriginallyBuiltBy
Indicates that a particular fortress was initially constructed by a specified builder or group.
-
B.
fortressWallBuiltInCentury
Indicates that a fortress wall was constructed during a specified century.
-
C.
fortressBuiltUnder
Indicates that one structure or location was constructed directly beneath or within the protective area of a fortress.
-
D.
eraOfFortification
Indicates the historical time period during which a structure or site was fortified or equipped with defensive works.
-
E.
eraOfMajorFortification
chosen
Indicates the historical period during which a structure or site underwent its primary or most significant phase of fortification.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21ebab54c81908d82dd6a26c406c2 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.