Triple
T987231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code Louis |
E21305
|
entity |
| Predicate | appliesFrom |
P22780
|
FINISHED |
| Object | late 17th 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 17th century | Statement: [Code Louis, appliesFrom, late 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesFrom Context triple: [Code Louis, appliesFrom, late 17th century]
-
A.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
B.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
appliesAcross
Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
-
D.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
E.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4a7754c8190a10ba0587bd8323d |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2abccbc8190a83af432f89eacf5 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b38630848190bd3898a4f42018ad |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.