Triple
T18954592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhein II |
E463737
|
entity |
| Predicate | collectorOrBuyer |
P7793
|
FINISHED |
| Object | anonymous buyer |
—
|
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: anonymous buyer | Statement: [Rhein II, collectorOrBuyer, anonymous buyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectorOrBuyer Context triple: [Rhein II, collectorOrBuyer, anonymous buyer]
-
A.
buyer
chosen
Indicates a relationship where one entity purchases or acquires goods, services, or rights from another entity in exchange for payment or compensation.
-
B.
seller
Indicates a relationship where one entity offers or provides goods, services, or assets to another in exchange for payment or other compensation.
-
C.
courtierOf
Indicates that one entity serves as a courtier in the court of another, typically a monarch or noble.
-
D.
collectedBy
Indicates that one entity has gathered, acquired, or assembled another entity, typically as part of a collection or data-gathering process.
-
E.
significantCollector
Indicates that an entity plays an important or notable role in collecting items, works, or data related to another entity.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d546babc81909d4fc5b6b4441aac |
completed | April 20, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon