Triple
T25467836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act V (Faust, Part Two) |
E638222
|
entity |
| Predicate | containsMottoOrLine |
P141177
|
FINISHED |
| Object | Das Ewig-Weibliche zieht uns hinan. |
—
|
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: Das Ewig-Weibliche zieht uns hinan. | Statement: [Act V (Faust, Part Two), containsMottoOrLine, Das Ewig-Weibliche zieht uns hinan.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMottoOrLine Context triple: [Act V (Faust, Part Two), containsMottoOrLine, Das Ewig-Weibliche zieht uns hinan.]
-
A.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
B.
mottoIncluded
chosen
Indicates that a motto is present as part of, or associated with, the referenced entity.
-
C.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
D.
hasPartInMotto
Indicates that something is included as a component or element within a motto.
-
E.
hasMottoScript
Indicates that an entity’s motto is written or expressed in a particular writing system or script.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 21, 2026, 2:19 p.m.