Triple
T16928719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łowicz |
E410645
|
entity |
| Predicate | wasPrivateTownOf |
P847
|
FINISHED |
| Object | Polish primates |
—
|
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: Polish primates | Statement: [Łowicz, wasPrivateTownOf, Polish primates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPrivateTownOf Context triple: [Łowicz, wasPrivateTownOf, Polish primates]
-
A.
fromTown
Indicates that one entity originates from, or is associated as being from, a particular town represented by the other entity.
-
B.
isInteriorTownOf
Indicates that one town is located within the interior region of, and is administratively or geographically associated with, a larger area or jurisdiction.
-
C.
hasTown
chosen
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
D.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
E.
isPlannedTown
Indicates that a town has been deliberately designed and constructed according to a pre-established plan rather than developing organically over time.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf23873c8190bdc9121d6c3850e2 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.