Triple
T20738449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Défense–Arc de Triomphe–Louvre axis |
E509773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical alignment |
C36007
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical alignment Context triple: [La Défense–Arc de Triomphe–Louvre axis, instanceOf, historical alignment]
-
A.
historical axis
chosen
A historical axis is a conceptual timeline or reference line that organizes events, periods, or developments in chronological order to reveal patterns and relationships across history.
-
B.
historical alliance
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural goals.
-
C.
historical relationship
A historical relationship is a connection between people, groups, or entities that existed in the past and is understood through documented events, interactions, and their lasting impact over time.
-
D.
historical position
A historical position is a specific role, office, or status held by an individual within a past social, political, or cultural context, defined by its responsibilities, authority, and time period.
-
E.
historical recognition
Historical recognition is the process by which individuals, events, or groups from the past are acknowledged, interpreted, and valued within collective memory and official narratives.
- F. None of above.
Provenance (1 batch)
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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:32 p.m.