Triple
T37325308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bi’ur |
E926584
|
entity |
| Predicate | scriptOfGermanText |
P103921
|
FINISHED |
| Object | Hebrew script |
—
|
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: Hebrew script | Statement: [Bi’ur, scriptOfGermanText, Hebrew script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOfGermanText Context triple: [Bi’ur, scriptOfGermanText, Hebrew script]
-
A.
textScript
chosen
Indicates the writing system or script in which a given piece of text is expressed.
-
B.
germanPart
Indicates that one entity is a component, section, or segment that belongs to or forms part of something specifically in a German context (e.g., language, jurisdiction, or origin).
-
C.
hasTitleInGerman
Indicates that an entity has a specific title or name expressed in the German language.
-
D.
GermanEditionURL
Indicates the URL where the German-language edition or version of an item can be accessed.
-
E.
scriptText
Indicates that one entity contains or represents the textual content of a script associated with 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:16 p.m.