Triple
T1088398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjou |
E24104
|
entity |
| Predicate | titleCreatedAs |
P13766
|
FINISHED |
| Object | county |
—
|
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: county | Statement: [Anjou, titleCreatedAs, county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCreatedAs Context triple: [Anjou, titleCreatedAs, county]
-
A.
createdAs
chosen
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
B.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of another entity.
-
C.
createdFor
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by another entity.
-
D.
createdUnder
Indicates that something was created during the time period or within the authority, rules, or conditions defined by another entity or context.
-
E.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b97d85708190a1630256648aa4a2 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b741b0cc8190be001a16a81f6d9e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.