Triple
T26420592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master of Flémalle |
E664226
|
entity |
| Predicate | placeNameOrigin |
P3325
|
FINISHED |
| Object | Flémalle near Liège |
—
|
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: Flémalle near Liège | Statement: [Master of Flémalle, placeNameOrigin, Flémalle near Liège]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeNameOrigin Context triple: [Master of Flémalle, placeNameOrigin, Flémalle near Liège]
-
A.
nameOriginExplanation
Indicates that an explanation is provided for the origin or derivation of a given name.
-
B.
seaNameEtymology
Indicates the origin or derivation of the name given to a particular sea.
-
C.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
districtNameOrigin
Indicates that the relationship specifies the origin or source from which a district’s name is derived.
-
E.
cityNamedAfter
Indicates that one city derives its name from or was named in honor of another entity, such as a person, place, or concept.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 26, 2026, 11:42 p.m.