Triple
T15591168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smurfette |
E374745
|
entity |
| Predicate | alignmentAfterTransformation |
P11169
|
FINISHED |
| Object | good |
—
|
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: good | Statement: [Smurfette, alignmentAfterTransformation, good]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentAfterTransformation Context triple: [Smurfette, alignmentAfterTransformation, good]
-
A.
alignmentShape
Indicates that one entity’s shape is arranged, oriented, or matched in position relative to another entity’s shape.
-
B.
alignmentChange
chosen
Indicates a change in the moral, ethical, or factional stance of an entity relative to its previous alignment.
-
C.
alignmentComponents
Indicates that one entity is composed of or associated with specific subparts or elements that together form its overall alignment.
-
D.
coordinateTransformation
Indicates a relationship where one coordinate system is mathematically converted or mapped into another, preserving the correspondence of points between them.
-
E.
laterAlignedWith
Indicates that one entity becomes aligned with or matches another entity at a later point in time, rather than initially.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e4b903c8190a35f9267cb38e721 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.