Triple
T1627480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Getting Out Our Dreams |
E35178
|
entity |
| Predicate | mottoDerivedFrom |
P30365
|
FINISHED |
| Object | Getting Out Our Dreams |
—
|
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: Getting Out Our Dreams | Statement: [Getting Out Our Dreams, mottoDerivedFrom, Getting Out Our Dreams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoDerivedFrom Context triple: [Getting Out Our Dreams, mottoDerivedFrom, Getting Out Our Dreams]
-
A.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
B.
mottoOriginal
Indicates that one entity is the original wording or form of another entity’s motto.
-
C.
motto
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
D.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
E.
mottoInterpretation
Indicates the explanatory relationship between a motto and its intended meaning or message.
- F. None of above. chosen
Provenance (4 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a94319becc819089c2daf45fe08a0c |
completed | March 5, 2026, 8:47 a.m. |
Created at: March 4, 2026, 7:28 p.m.