Triple
T243626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Histoire des guerres civiles de France |
E4987
|
entity |
| Predicate | historicalMethod |
P9744
|
FINISHED |
| Object | narrative history |
—
|
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: narrative history | Statement: [Histoire des guerres civiles de France, historicalMethod, narrative history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMethod Context triple: [Histoire des guerres civiles de France, historicalMethod, narrative history]
-
A.
historicalFunction
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
B.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
C.
historicalAssessment
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
D.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
E.
historicalScript
Indicates that an entity is or was written in, or otherwise associated with, a particular historical writing system or script.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b62839c8190824064fe5da6a92a |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25dcba5148190ab80fd14c7cf4bb4 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.