Triple
T24644883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingauni |
E610077
|
entity |
| Predicate | ancientSettlementAt |
P108844
|
FINISHED |
| Object | Albingaunum |
—
|
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: Albingaunum | Statement: [Ingauni, ancientSettlementAt, Albingaunum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancientSettlementAt Context triple: [Ingauni, ancientSettlementAt, Albingaunum]
-
A.
earliestPermanentSettlement
Indicates that one entity is the location or instance of the first long-term, continuously inhabited settlement associated with another entity.
-
B.
ancientNameOfServedSettlement
Indicates that the object is an earlier or historical name by which the settlement served by the subject was known.
-
C.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
D.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
-
E.
hasArchaeologicalSiteIn
chosen
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:33 a.m.