Triple
T31473478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freihung (partly) |
E802923
|
entity |
| Predicate | hasPartiallyLocatedIn |
P15446
|
FINISHED |
| Object | Freihung |
—
|
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: Freihung | Statement: [Freihung (partly), hasPartiallyLocatedIn, Freihung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartiallyLocatedIn Context triple: [Freihung (partly), hasPartiallyLocatedIn, Freihung]
-
A.
partlyLocatedOn
chosen
Indicates that one entity is situated such that only a portion of it lies on or within the spatial extent of another entity.
-
B.
partlyLocatedNear
Indicates that one entity is situated near another, but only a portion or subset of it lies within that nearby area.
-
C.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
D.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
E.
partlyLocatedInTimeZone
Indicates that an entity’s extent overlaps multiple time zones, with at least part of it falling within the specified time zone.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: April 30, 2026, 9:27 p.m.