Triple
T30254071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Geißböcke |
E769287
|
entity |
| Predicate | hasPluralMeaning |
P10718
|
FINISHED |
| Object | multiple billy goats |
—
|
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: multiple billy goats | Statement: [Die Geißböcke, hasPluralMeaning, multiple billy goats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPluralMeaning Context triple: [Die Geißböcke, hasPluralMeaning, multiple billy goats]
-
A.
hasMultipleMeanings
Indicates that a term, symbol, or expression is associated with more than one distinct meaning or interpretation.
-
B.
hasMeaningInOriginLanguage
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
C.
hasPluralForm
Indicates that one term is the plural grammatical form of another term.
-
D.
hasMeaningExtension
Indicates that one entity represents an extended, elaborated, or more detailed meaning of another entity’s meaning.
-
E.
possibleMeaning
chosen
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 7:40 p.m.