Triple
T25858515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year XII |
E651416
|
entity |
| Predicate | timeInForceIn |
P38735
|
FINISHED |
| Object | French Consulate |
—
|
NE NERFINISHED |
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: French Consulate | Statement: [Year XII, timeInForceIn, French Consulate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInForceIn Context triple: [Year XII, timeInForceIn, French Consulate]
-
A.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
B.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
C.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
D.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
-
E.
timeFrameSpecified
chosen
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60269c0fc8190a73fa347f8d99281 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:04 a.m.