Triple
T18689444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curly Howard as the childlike stooge |
E456951
|
entity |
| Predicate | typicalDynamic |
P126659
|
FINISHED |
| Object | submissive to Moe |
—
|
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: submissive to Moe | Statement: [Curly Howard as the childlike stooge, typicalDynamic, submissive to Moe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDynamic Context triple: [Curly Howard as the childlike stooge, typicalDynamic, submissive to Moe]
-
A.
typicalDynamics
chosen
Indicates the usual or characteristic way in which a system, process, or interaction evolves or behaves over time.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
D.
typicalMovement
Indicates the usual or characteristic way in which an entity moves or is expected to move.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2fc2cc8190a4726526a714a5eb |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.