Triple
T33013440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Portugal |
E844707
|
entity |
| Predicate | foundingEventDate |
P41
|
FINISHED |
| Object | 868 |
—
|
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: 868 | Statement: [County of Portugal, foundingEventDate, 868]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingEventDate Context triple: [County of Portugal, foundingEventDate, 868]
-
A.
foundedOn
chosen
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
B.
foundedOnOccasionOf
Indicates that something was established or created specifically in response to, or to mark, a particular event or occasion.
-
C.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
D.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
E.
foundingLegendDate
Indicates the date associated with the legendary or mythic founding of an entity, rather than its historically verified establishment date.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 1, 2026, 1:23 a.m.